- From: <bugzilla@jessica.w3.org>
- Date: Sun, 14 Aug 2011 21:00:47 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13423 Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bhawkeslewis@googlemail.com --- Comment #8 from Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> 2011-08-14 21:00:46 UTC --- WG Member here. If the existing text is a subset of what is being implemented, that's no different to the rest of the frozen W3C spec. But if it contradicts what is being implemented to the extent that clientside code written against the spec will fail, that will cause authors confusion and users may experience breakage. (Implementor feedback would be valuable as to which is the case here.) I don't think we should leave such contradictions in the spec. I'm ambivalent about whether that's corrected by fixing the HTML draft itself, by splitting it out into a second HTML WG document, or by making it a Webapps responsibility. Our WG charter suggests any of these options would be fine, but editing APIs were supposed to be one of our deliverables. Worst case scenario: if nobody volunteers to maintain this text within the W3C space, I'd still rather we remove the text containing the contradictions. Just my 2 cents. -- 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 Sunday, 14 August 2011 21:00:48 UTC