This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

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
Summary: Redefining elements can cause compatibility issues. What if some browsers rea...
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-09 02:17 UTC by contributor
Modified: 2010-10-04 14:32 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-05-09 02:17:50 UTC 
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
Comment 1 Ian 'Hixie' Hickson 2010-08-24 22:28:09 UTC 
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?