[Bug 9690] Redefining elements can cause compatibility issues. What if some browsers read it the old way, and some the new way. This can lead to problems if someone uses the element the new way, only for it to be read the old way, or for old documents to require rew

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


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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |NEEDSINFO




--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-08-24 22:28:09 ---
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: Did Not Understand Request
Change Description: no spec change
Rationale: I don't understand. Could you elaborate? What specific compatibility
issue did you have in mind?

-- 
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, 24 August 2010 22:28:10 UTC