Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Should the special handling of <isindex> be removed? #240
Comments
karlcow
commented
Apr 22, 2016
|
Given the dependency on the server side and its non implementation across some browsers. From a Web compatibility point of view, it doesn't create any issues to remove it. And it doesn't seem to be a big change either for Firefox, but @hsivonen will know better |
arronei
added a commit
to arronei/html
that referenced
this issue
Apr 22, 2016
|
|
arronei |
64dc7eb
|
|
Sounds like @hsivonen responded in https://bugzilla.mozilla.org/show_bug.cgi?id=1266495 confirming OK to remove. Also was removed from WHATWG. This SGTM. |
travisleithead
closed this
Apr 22, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
travisleithead commentedApr 21, 2016
This was started as an editorial change in PR #238, but want to make sure this is resolved as decision of the WG.
See Bugzilla bug: https://www.w3.org/Bugs/Public/show_bug.cgi?id=28326
Parser support for the inflation of
<isindex>into multiple DOM nodes as described currently in the spec appears to exist in Safari (latest?) and Mozilla. Chrome and Edge have dropped their handling of this element.Mozilla had some feedback, haven't heard from Safari reps.
@arronei @karlcow @annevk @hober @hsivonen @rniwa