9690 2010-05-09 02:17:50 +0000 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 2010-10-04 14:32:05 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED NEEDSINFO http://www.whatwg.org/specs/web-apps/current-work/#presentational-markup P3 normal LC 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 35525 0 contributor 2010-05-09 02:17:50 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#presentational-markup Comment: 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 rewriting due to compatibility issues. Posted from: 203.160.123.142 37798 1 ian 2010-08-24 22:28:09 +0000 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?