Closed
Bug 326369
Opened 20 years ago
Closed 20 years ago
Drop support for <isindex>
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: ian, Unassigned)
References
Details
According to my study of one billion Web pages, less than 0.0013% of pages use the <isindex> element. In fact, so few pages use it that it didn't appear on my top 1000 most-used elements list, meaning it was used less than <side_ads>, <preform>, <titolo>, <bdbereich>, <org>, <cunet>, <l1>, <hot:trolley>, and numerous other bogus elements.
<isindex> has numerous bugs, and Mozilla's support for it differs from Safari's, IE's, and Opera's.
I would like to drop support for parsing <isindex> specially in HTML5. If it turns out that <isindex> _is_ in fact used, then we'll find out about it soon and can change the HTML5 spec so that it is clear how it should be implemented.
Reporter | ||
Comment 1•20 years ago
|
||
(o195531, w7139)
If 0.0013% of one billion pages use isindex that means that we'd break 13000 pages by dropping support for isindex. I'd rather not do that without having a good reason.
Seems like isindex works fairly well as it stands, the only issue is that we don't support the action attribute, and that css doesn't work. I wouldn't be entierly opposed the idea to do what IE (and possibly other browsers) do and rather then having a real <isindex> element output markup that amounts to the same thing. That would also fix bug 93795 which is not about the isindex element.
Reporter | ||
Comment 3•20 years ago
|
||
Less than 0.013%, not 0.013%. (Due to the way I did the survey, the cut-off limit was at 0.013%.) A separate survey I became aware of last night, which checked about 150000 pages, found around 0.005% (7 pages) with <isindex>.
I'm happy to make HTML5 do what IE does (in fact I've basically already specced it, it's just comment out right now). However, if we can get away with dropping support altogether, I'd rather do that -- hence this bug.
Reporter | ||
Comment 4•20 years ago
|
||
(er, 0.0013%, not 0.013%. And yes, the smaller survey had a bigger proportion of sites with <isindex>, which may have been due to sample bias; the point was just to clear up that it was definitely more than 0 sites, i.e. that <isindex> is definitely used, just not much.)
One alternative is to drop it from the HTML5 spec and leave it up to those browser vendors that care support it anyway.
I am uncomfortable dropping support for this element, aweful as it is. But i'd welcome any changes that simplify its implementation.
Reporter | ||
Comment 6•20 years ago
|
||
No, dropping support from it in HTML5 and having people support it anyway is not an option.
I'll put <isindex> in the spec. Thanks for the feedback!
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
Comment 7•19 years ago
|
||
Maybe <isindex> could be implemented in xbl (or am I saying something stupid here?)?
You need to log in
before you can comment on or make changes to this bug.
Description
•