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 28326 - Remove isindex parsing logic
Summary: Remove isindex parsing logic
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P1 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
Whiteboard: whatwg-resolved
Depends on:
Reported: 2015-03-24 19:37 UTC by Travis Leithead [MSFT]
Modified: 2016-10-25 09:17 UTC (History)
9 users (show)

See Also:


Description Travis Leithead [MSFT] 2015-03-24 19:37:24 UTC
The purpose of this bug is to drive consensus on whether the special-case isindex parsing logic should be removed from the HTML spec.

In [1] we see the discussion and ensuing removal of this logic from Google's Blink engine (affecting two user agents).

Most recently, in Microsoft's Project Spartan, we've followed Blink's lead for interop. It's too early for us to tell the effect on our compatibility that this will have. Now we will have two browser engines not supporting the parser's fix-up logic. I'd like to see at least Firefox join us and get the spec updated to remove this special case logic to legitimize these recent changes. If not, perhaps there is good reason to keep the spec as-is, and possible reverse Project Spartan's recent decision.

Reasons to remove:
* I've heard that XSS bypass attacks are more easily possible (the original concern for the Blink removal).
* Very little usage of the legacy tag (isindex).

Reasons to keep
* Compatibility with early HTML

Comment 1 Karl Dubost 2015-03-25 00:46:06 UTC
Historical context of isindex

On Mozilla bug tracker
Something related to isindex [1]
There's no specific bug asking the removal of isindex (as of today). 

The latest modifications touching isindex on the tree builder code seems to be Fri, 31 Jan 2014 15:03:24 -0800 [2]

I guess Henri Sivonen would know better.

Comment 2 Anne 2015-03-25 10:15:24 UTC
For Mozilla I think this is largely up to Henri coupled with a change to the WHATWG specification.
Comment 3 Michael[tm] Smith 2015-06-16 10:26:51 UTC
Making this a higher priority to actively seek more feedback on from implementers and webdevs.
Comment 4 Arron Eicholz 2016-04-21 17:21:09 UTC
HTML5.1 Bugzilla Bug Triage: Fixed

This has been removed from the latest draft
Comment 5 Anne 2016-04-21 17:34:17 UTC
Curious decision policy where you ignore the only bit of feedback.
Comment 6 Domenic Denicola 2016-04-21 17:45:25 UTC
It wasn't removed: contains the same contents as which maintains support for isindex special parsing.
Comment 7 Arron Eicholz 2016-04-21 18:50:01 UTC
@Anne the isindex element is not supported by Edge and Chrome. Safari, and Firefox still have support for this at this time but we figure it is better to remove stuff from HTML5.1 that has a higher likelihood of going away than to keep stuff. If you think this needs to be kept in the spec. Please open an issue on github or respond to the PR [1].

@Domenic I accidentally hit save change on this before I finished my PR. I was hopeful no one would notice this change until finished writing my PR.

[1] -