Re: Intent to Use Counter: Everything

2016-05-11 Thread Boris Zbarsky
On 5/11/16 12:46 PM, Mike Taylor wrote: Is there any handy way of identifying these, other than cross-referencing with the relevant specs? Generally they are in a separate partial interface in the webidl file. And typically that partial interface is documented as non-standard or Gecko-only

Re: Intent to Use Counter: Everything

2016-05-11 Thread Mike Taylor
On 5/11/16 3:56 AM, Cameron McCormack wrote: Recording use counter information as we parse CSS is not too expensive, although if we were doing it for all ~300 properties I’d be wanting to check that we don’t slow sheet parsing speed down appreciably. It’s probably fine, but see the work that is

Re: Intent to Use Counter: Everything

2016-05-11 Thread Mike Taylor
On 5/10/16 6:53 PM, Jonas Sicking wrote: The moz-isms aren't as easy to spot in the DOM since there's much less of a history of prefixing DOM-API names, but they certainly exist. Is there any handy way of identifying these, other than cross-referencing with the relevant specs? -- Mike

Re: Intent to Use Counter: Everything

2016-05-11 Thread Cameron McCormack
Mike Taylor: > Having recently discovered UseCounters.conf[1], I'd like to add use > counters for all CSS properties, starting with prefixed props. And > likewise for Moz-prefixed DOM props and methods. > > Ultimately, I'd like us to have a Firefox equivalent to >

Re: Intent to Use Counter: Everything

2016-05-10 Thread Jonas Sicking
On Tue, May 10, 2016 at 1:31 PM, Mike Taylor wrote: > On 5/10/16 3: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

Re: Intent to Use Counter: Everything

2016-05-10 Thread Mike Taylor
On 5/10/16 3: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

Re: Intent to Use Counter: Everything

2016-05-10 Thread Steve Fink
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

Re: Intent to Use Counter: Everything

2016-05-10 Thread Jack Moffitt
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

Re: Intent to Use Counter: Everything

2016-05-10 Thread Mike Taylor
On 5/10/16 2:11 PM, Mike Taylor wrote: Having recently discovered UseCounters.conf[1], I'd like to add use counters for all CSS properties, starting with prefixed props. And likewise for Moz-prefixed DOM props and methods. Link to bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1271752 --