[Bug 22498] Inconsistency in explanation of fragment ID resolving vs. anchor element specs

https://www.w3.org/Bugs/Public/show_bug.cgi?id=22498

--- Comment #2 from Áxel Costas Pena <axl.coding@gmail.com> ---
> ... to discourage certain features that are only allowed in very few circumstances ... These are generally old obsolete features that have no effect, and are allowed only to distinguish between likely mistakes ... and mere vestigial markup or unusual and discouraged practices ...

This paragraph seems meaning that you should be killed if you use those
features in a new HTML5 web you're building... In the other hand, the fragment
resolving instructions seems being explaining a feature and encouraging you to
use when you consider it matches your requirements or it fits well your
design...

If both informations are kept, I'd at least include a footnote on:
> 5. If there is an element in the DOM that has an ID exactly equal to decoded fragid, then the first such element in tree order is the indicated part of the document; stop the algorithm here.
clarifying that despite the fact that this works this way, this is a vestigial
feature and developers are encouraged to avoid using it...

What do you think?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Saturday, 29 June 2013 15:28:52 UTC