Re: twitter, document.all

Thanks for the clarification. This is much less surprising. Sorry for spreading misinformation, I will follow up.

Dave

----- Original Message -----
From: Ms2ger <ms2ger@gmail.com>
To: dherman@mozilla.com, continuation@gmail.com, doug turner <doug.turner@gmail.com>
Cc: www-archive@w3.org
Sent: Thu, 13 Feb 2014 02:42:45 -0800 (PST)
Subject: Re: twitter, document.all

I felt I should correct some misunderstandings:

* document.all.tags is not necessary for web compat; sicking 
accidentally broke it in bug 259332, and I removed some traces in bug 
874084. Google gets 0.001% on its UseCounter, so they removed it in 
https://code.google.com/p/chromium/issues/detail?id=290891. Hixie 
removed it from the spec in 
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22118.

* document.all(foo) was claimed to have 0.00% usage in 
https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/urMtTTPpUro/, 
so I tried to remove it in bug 969030. A broken site was discovered 
yesterday, so I backed it out this morning. It then turned out that the 
0.00% figure was wrong; the correct figure was 0.03%. Hixie also removed 
this in https://www.w3.org/Bugs/Public/show_bug.cgi?id=22118, and will 
restore it based on the new data.

* document.all itself used to be implemented in IE as a truthy object, 
and is widely used to detect old IEs. In IE11, as they became a lot 
closer to other browsers, document.all-detecting code paths tended to 
break, so IE11 has a falsy document.all, like all other browsers. 
https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/urMtTTPpUro/ 
was based on two misunderstandings, so won't actually happen. The 
correct figure here seems to be 4.86%, which is much too high to remove 
it. (It is not clear to me if that figure includes detecting as well as 
actual usage.) Nobody will fully remove it in the foreseeable future.

HTH
Ms2ger

Received on Thursday, 13 February 2014 14:14:22 UTC