Summary: | IE-only supports <comment> tag | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | jasneet <jasneet> | ||||||
Component: | DOM | Assignee: | Nobody <webkit-unassigned> | ||||||
Status: | RESOLVED INVALID | ||||||||
Severity: | Normal | CC: | ahmad.saleem792, ap, bfulgham, jasneet, rniwa, webkit | ||||||
Priority: | P2 | Keywords: | HasReduction | ||||||
Version: | 525.x (Safari 3.1) | ||||||||
Hardware: | PC | ||||||||
OS: | Windows XP | ||||||||
URL: | http://classadnew.sina.com.cn/user/info_fix.php?f_city=556&f_id=1624659 | ||||||||
Attachments: |
|
Description
jasneet
2008-03-28 16:34:06 PDT
Created attachment 20170 [details]
screenshot
Created attachment 20171 [details]
reduction
Since it's non-standard element and also not supported by other browsers (except IE) there is no reason to implement it. Sure there is: site compat. A good reason _not_ to implement would be "doing this will break x, y, and z". Obviously there's an opportunity to evangelize the site to only use standards-compliant tags, but that doesn't also preclude consideration of support for this IE-ism if it increases real-world compat and doesn't break things. Confirmed as an evangelism bug. This is trivial to support. The danger in supporting it would be with tag misnesting, since an error in closing the tag could result in a pretty catastrophic rendering failure. We'd have to make sure we understood IE's error resolution for the tag before turning it on. comment { display: none } in the CSS file is all that is required to implement this. Given that Firefox and Opera don't support it, it's hard to imagine that this is that important though. hyatt: note the domain of the problem site. no browser except IE has marketshare in china. No the browser support it event today (Safari 15.6, Chrome Canary 106 and Firefox Nightly 104). I think this can be marked as "RESOLVED WONTFIX"? Thanks! |