[Bug 14346] New: This section assumes that a single character token is returned from the consume a character reference algorithm. But it now can return two characters instead of one, and that needs to be reflected here. Also in the two other places that the algorithm is

http://www.w3.org/Bugs/Public/show_bug.cgi?id=14346

           Summary: This section assumes that a single character token is
                    returned from the consume a character reference
                    algorithm. But it now can return two characters
                    instead of one, and that needs to be reflected here.
                    Also in the two other places that the algorithm is
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#cha
                    racter-reference-in-data-state
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


Specification:
http://www.whatwg.org/specs/web-apps/current-work/multipage/tokenization.html
Multipage: http://www.whatwg.org/C#character-reference-in-data-state
Complete: http://www.whatwg.org/c#character-reference-in-data-state

Comment:
This section assumes that a single character token is returned from the
consume a character reference algorithm. But it now can return two characters
instead of one, and that needs to be reflected here.  Also in the two other
places that the algorithm is referenced.

Posted from: 66.114.38.251
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0a2)
Gecko/20110927 Firefox/8.0a2

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Friday, 30 September 2011 18:00:52 UTC