As suspected, enumeration was a big contributor, at the counter is now dropping:Based on counters that have been removed entirely in previous releases, it looks like it will take long time to settle:I'll wait a bit longer before poking at offscreenBuffering, but since enumeration seems to contribute at least 0.1% on window attributes, I'd also like to make the following non-standard attributes on window not enumerable:clientInformationdefaultStatusdefaultstatusorientationscreenLeftscreenTopstyleMediawebkitURLWebKitAnimationEventWebKitMutationObserverWebKitTransitionEventDoes that seem OK? It's not entirely without risk, so if there are any of these that we think should stay long-term (and be standardized) we shouldn't mess with them.PhilipOn Wed, Dec 3, 2014 at 4:30 AM, Philip Jägenstedt <phi...@opera.com> wrote:OK, let's try that, if nothing else it will give us an idea of how much "noise" enumeration contributes.PhilipOn Tue, Dec 2, 2014 at 8:13 PM, Chris Harrelson <chri...@chromium.org> wrote:Since this attribute is not getting in the way, how about we first make it not enumerable, and see if usage drops? 0.18% is a lot.On Tue, Dec 2, 2014 at 1:50 AM, Philip Jägenstedt <phi...@opera.com> wrote:On Tue, Dec 2, 2014 at 10:46 AM, TAMURA, Kent <tk...@chromium.org> wrote:
>
> Basically LGTM.
>
> > That's around ~0.18%, far above what we would usually try removing.
>
> It's high. I recommend to remove this just after branch so that we can have enough time to find serious issues.
Good idea, I'll do the removal in mid-January assuming this thread
gets another LGTM.
Philip
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
MDN is a fine place for this. The W3C has made WPD particularly difficult to improve.
Better that we have up-to-date information for developers where they are likely to find it.
Regards
Well, some APIs (like window.clientInformation, an alias of navigator) are useless and should be removed if possible, while some (like window.find()) possibly do something useful. It's a good rule of thumb to avoid all non-standard APIs, but to offer advice to developers on a specific API needs at least a few minutes of analysis.
If anyone wants to invest that time, I think it would be useful if when searching for, say, clientInformation, the first result is a page explaining that's it's useless and not supported in all browsers.
Philip