On 05/10/2016 01:05 PM, Jack Moffitt wrote:
We have the Chrome popularity data, and we have the Edge team's data
which covers the CSS spectrum quite well. I think it would be far more
useful to start covering the DOM API spectrum.
For example, it's pretty clear from existing data sources which CSS
properties Servo should focus on. But we have very little data for
which DOM APIs are important.
What value does having even more CSS property data provide above and
beyond the value that can be extracted from the existing sources? Is
that value greater than the value we could extract by focusing on data
that doesn't currently exist?
I assume the answer to the first question is that it gives us data
that doesn't exist about -moz prefixed properties. Regarding the
second question, my opinion is that we can get a lot more benefit from
covering other areas than CSS. I'm curious to hear more informed
opinions on this than my own.
As to where this should live, it seems unfortunate that we would end
up with three repositories of data: Chrome's use counters, Edge's
platform status, and now a Mozilla one. Is it not possible to
consolidate this collection effort?
Why is this an either/or? Both seem valuable.
Multiple data sources provide opportunities to detect discrepancies
between them. (eg, say feature-detection triggers a hit count in one
browser's collection mechanism and not another's.) I agree that a
unified reporting facility would be useful. But I'd bet we'd learn
*something* by looking at where our numbers mismatch other browsers'.
Another example: consider the case where UA detection prevents the usage
of a CSS property. If everyone avoids a particular CSS property on
Firefox only, perhaps there is a real reason for it that we should
figure out. Maybe we need to evangelize the fact that we now support
property X, or have fixed the bug causing it to be blacklisted.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
