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 22118 - Remove support for document.all.tags
Summary: Remove support for document.all.tags
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 minor
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-21 13:52 UTC by contributor
Modified: 2014-02-21 22:12 UTC (History)
6 users (show)

See Also:


Attachments

Description contributor 2013-05-21 13:52:54 UTC
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/common-dom-interfaces.html
Multipage: http://www.whatwg.org/C#htmlallcollection-0
Complete: http://www.whatwg.org/c#htmlallcollection-0
Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/

Comment:
Remove support for document.all.tags

Posted from: 87.64.214.136 by ms2ger@gmail.com
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20130421 Firefox/23.0
Comment 1 Ms2ger 2013-05-21 14:04:22 UTC
Gecko hasn't has working support for it since Firefox 3.
Comment 2 Ian 'Hixie' Hickson 2013-06-11 22:03:51 UTC
Is anyone else planning on dropping it?
Comment 3 Ms2ger 2013-06-12 06:40:29 UTC
Tab, do I recall correctly that you were looking at this in Blink?
Comment 4 Tab Atkins Jr. 2013-06-12 07:10:24 UTC
I haven't yet done so, but I can add a use tracker when I get back to my desk next week.
Comment 6 Boris Zbarsky 2014-02-06 15:39:24 UTC
From blink-dev's "Intent to Deprecate and Remove: document.all." thread:

  We also have trackers for DocumentAllLegacyCall (0.00%) (using
  HTMLAllCollection as a function) and DocumentAllTags (0.00%).

So can we nix both of those?  ;)

I believe Firefox right now supports the legacycaller but but not .tags.
Comment 7 Boris Zbarsky 2014-02-06 16:23:44 UTC
From the Chromium bug cited in comment 5:

  We got 0.001% for our DocumentAllTags UseCounter.

  Conclusion: Safe to remove.
Comment 8 Ian 'Hixie' Hickson 2014-02-06 19:35:14 UTC
That's fantastic. Removed!
Comment 9 contributor 2014-02-06 19:35:22 UTC
Checked in as WHATWG revision r8469.
Check-in comment: Remove some parts of document.all that data shows have virtually no usage.
http://html5.org/tools/web-apps-tracker?from=8468&to=8469
Comment 10 Boris Zbarsky 2014-02-12 21:24:45 UTC
More from blink-dev:

  FWIW, this number is wrong. Looking at Chrome's latest stable release on
  Windows, DocumentAllLegacyCall is used on 0.03% of sites. We've still been
  figuring out what the lower bound is on features we can safely remove, so this
  is a useful data point that 0.03% is likely too high.
Comment 11 Ian 'Hixie' Hickson 2014-02-12 22:57:15 UTC
Reopening to track likely reversion of at least the legacycaller stuff. :-(
Comment 12 contributor 2014-02-21 22:12:49 UTC
Checked in as WHATWG revision r8502.
Check-in comment: Restore document.all() legacycaller, for compat
http://html5.org/tools/web-apps-tracker?from=8501&to=8502