W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > May 2010

[Bug 9659] New: Initial U+0000 should not set frameset-ok to "not ok"

From: <bugzilla@jessica.w3.org>
Date: Wed, 05 May 2010 07:33:27 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-9659-2486@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9659

           Summary: Initial U+0000 should not set frameset-ok to "not ok"
           Product: HTML WG
           Version: unspecified
          Platform: All
               URL: https://bugzilla.mozilla.org/show_bug.cgi?id=563526
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec bugs
        AssignedTo: dave.null@w3.org
        ReportedBy: hsivonen@iki.fi
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org, public-html@w3.org


According to https://bugzilla.mozilla.org/show_bug.cgi?id=563526 , the D-Link
DSL-G604T ADSL router has a zero byte in its configuration UI before a
<frameset>. This causes the HTML5 parsing algorithm to first turn the zero byte
into the REPLACEMENT CHARACTER which flips frameset-ok to "not ok" which causes
the frameset to be discarded.

It's a pretty serious problem if a user can no longer change the router
configuration after upgrading his/her browser, so I think a change to the
parsing algorithm is needed.

I suggest making the tokenizer signal to the tree builder that a U+FFFD used to
be a U+0000 in the data state (as opposed to being a literal U+FFFD or an NCR)
and making the tree builder discard U+0000 mapped to U+FFFD in the initial
insertion mode.

-- 
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 Wednesday, 5 May 2010 07:33:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:17 UTC