W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > June 2008

[Bug 5752] Parsing should be specified for future updates

From: <bugzilla@wiggum.w3.org>
Date: Sat, 21 Jun 2008 17:56:09 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1KA7Jp-0008FX-L1@wiggum.w3.org>

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


Rob Burns <rob@robburns.com> changed:

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




--- Comment #21 from Rob Burns <rob@robburns.com>  2008-06-21 17:56:09 ---
I don't think it is appropriate to close this bug. There are some very
important issues here that should at be aired to the entire WG if they cannot
be resolved here. The comments against fixing this bug relate to the
complications of specifying parsing and the resistance of UA vendors to
changing their parsing. However, the HTML5 draft already specifies parsing. The
question then is if we are going to specify something complex and which UAs
will be resistant to adopting in the first place; then should we specify
changes that will not make it any easier to update HTML semantics in the
future? I definitely don't think we should do that (which is what the current
draft does). If on the other hand you want to close this bug for the reasons
stated, then that implies we're going to remove the entire parsing section of
the HTML5 draft.


-- 
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 Saturday, 21 June 2008 17:56:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 21 June 2008 17:56:45 GMT