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

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

            Bug ID: 22498
           Summary: Inconsistency in explanation of fragment ID resolving
                    vs. anchor element specs
    Classification: Unclassified
           Product: HTML WG
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec
          Assignee: dave.null@w3.org
          Reporter: axl.coding@gmail.com
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-admin@w3.org,
                    public-html-wg-issue-tracking@w3.org

In www.w3.org/html/wg/drafts/html/master/browsers.html#scroll-to-fragid we can
read:
"No decoded fragid: If there is an a element in the DOM that has a name
attribute whose value is exactly equal to fragid (not decoded fragid), then the
first such element in tree order is the indicated part of the document; stop
the algorithm here."

That is inconsistent with anchor specs at
http://www.w3.org/html/wg/drafts/html/master/text-level-semantics.html#the-a-element
which doesn't define a name attribute for anchor elements.

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

Received on Thursday, 27 June 2013 20:46:06 UTC