[csswg-drafts] [css-content] Need to clarify in-flow presentation implications for bookmarks

drmacro has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-content] Need to clarify in-flow presentation implications for bookmarks ==
In reference to the Editor’s Draft, 24 January 2018:

https://drafts.csswg.org/css-content/#bookmark-generation

The section on bookmarks does not indicate whether or not elements styled with bookmark-* properties are presented in the main flow as well as generating bookmarks.

I have both use cases in documents I am publishing now:

Case 1: Existing print ToC also produces bookmarks.
Case 2: PDF bookmarks must be different from print ToC

In Case 1 it is convenient to simply add bookmark properties to existing ToC elements. I'm using this technique with Antenna House Formatter today, for example. 

In Case 2 the PDF bookmarks need to be different from the ToC in some way. In my case, the PDF bookmarks need to be more complete than the ToC, which only reflects the top 2 or 3 levels in the publication hierarchy.

I noticed note 20. 

I would support requiring bookmarks to be generated from display: none elements. However, I can see that some users might complain that that prevents turning off bookmarks entirely by simply hiding the bookmark-generating structure.

A more complete solution would be to provide some type of "bookmark only" indicator. Typical markup practice would be to have a root element that then contains the bookmark-generating elements, e.g.:

```
<div class="bookmarks">
  <div class="bookmark" label="This is the first bookmark" target="#id-01"/>
  <div class="bookmark" label="This is the second bookmark" target="#id-02"/>
  ...
</div>
```

A property that could go on the .bookmarks div to indicate that it is used exclusively for bookmarks  would address the requirement.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2734 using your GitHub account

Received on Monday, 4 June 2018 01:41:53 UTC