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

[Bug 10803] Ignore document.written charset metas

From: <bugzilla@jessica.w3.org>
Date: Tue, 07 Dec 2010 21:08:49 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PQ4mH-00064Q-Lu@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10803

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #12 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-12-07 21:08:48 UTC ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: Optimising the spec for the particular implementation in Gecko seems
like a bad idea, given how esoteric that implementation is. WebKit simply
doesn't handle <meta> from inside the parser at all, which is why it doesn't
handle it from within script. Opera does seem to handle it from scripts. I
can't work out what IE does, but the IE parser is not yet close to matching the
HTML spec in many ways, so it will likely need significant work anyway and thus
the simpler the work the better, if we are to get interop.

Thus, in the absence of concrete compatibility constraints, I still think that
it's best to have the parser here be as conceptually simple as possible. It
does not seem to me that it would be hard to implement the spec, even in Gecko,
and it _does_ seem that it would be harder to implement the spec as you
describe, in the general case. It seems highly unlikely that the majority of
implementations will end up with HTML parsing being multithreaded in the way
you describe.

-- 
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 Tuesday, 7 December 2010 21:08:51 UTC

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