On 12/15/16 6:15 PM, Ehsan Akhgari wrote:
(I personally agree with most of what you said, except that I'm
convinced that we should expose that one bit.)
Exposing this one bit makes a lot of sense to me.
From a more practical perspective, we have two shipping implementations
of this API. What are you proposing to do with that for starters?
After we finish crying? I think we fundamentally have two options:
1) Create a new API, convince everyone to ship it and deprecate the
other thing, and eventually hopefully remove it.
2) Figure out a way to map the one bit of information we actually want
to expose into some sort of values that look like the existing API.
Change the spec as needed to allow tweaks we want to make here (e.g. to
allow having the max speed thing not be defined or always be 0 or always
+Infinity, or always NaN, or always 42 or something).
Note that Chrome has some use counters on this API:
Right, those are all above their removal thresholds. But I should note
that we've recently removed other things with high use counters once we
determined that a lot of that was from tracking scripts... That said,
the NetInfoOnChange counter is not likely to be tracking script.
I assume this is just data from Chrome, not webviews?
-Boris
P.S. I wish our DOM counters had a display like this, both in terms of
searchability and performance. :(
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
