- From: <bugzilla@jessica.w3.org>
- Date: Mon, 22 Jul 2013 23:25:04 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20319
Travis Leithead [MSFT] <travil@microsoft.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |travil@microsoft.com
--- Comment #2 from Travis Leithead [MSFT] <travil@microsoft.com> ---
See: http://html5.org/tools/web-apps-tracker?from=5641&to=5642
It seems a little weird to want to "fix" this bug when all of the major recent
browsers are 100% consistent on their parsing behavior in this scenario--e.g.,
we've successfully achieved an interoperable HTML5 parser!
What's so bad about leaving the current limits in place? I.e., is there a site
compatibility bug that is motivating this change, or is it simply altruistic?
The linked bug above describes "practical limits" for the AAA which seem to
have resulted in this problem. Yet, if this isn't really a "problem" for web
content somewhere, then why fix it?
My inclination is to Won't Fix this bug and call this an interesting anomaly of
the AAA (and move on). There's enough other bizarre features of the HTML5
parser that I'm pretty comfortable with that idea.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 22 July 2013 23:25:06 UTC