-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hidden elements #5
Comments
This plugin implements the outlining as defined in the HTML spec: http://www.w3.org/TR/html5/sections.html#outline. So, the request to ignore elements with "display: none;" is a valid one, but really does belong over there. I'm pretty sure they've also discussed it... However, it is worth noting, that the algorithm does ignore the elements with a Honestly, I do not think it's a good idea to implement this request per se, because it mixes presentational (CSS) and markup (HTML) data, but I think it might be worth highlighting in the outline that a section (and maybe its header) is fully invisible due to |
|
I don't think I agree that it has the same meaning. For one, it's CSS and not HTML - that alone gives it a completely different context. And like I mentioned before - the algorithm does not define this, so I'm reluctant to make it [not a] part of the outline. |
The As for elements hidden with CSS ( |
I'm wondering whether hidden elements should be part of the outline. Depends on how you use the tool.
If it's to see the current document structure as a screen reader or browser would parse it, hidden elements should not be part of the outline.
Maybe there should be a setting or something in the plugin for this.
By hidden elements I mean those that a screen reader would not read out; computed CSS with display: none.
The text was updated successfully, but these errors were encountered: