Thanks, Manish! This is a cool reference. It's interesting to see Stylo
has implemented exactly one property that Gecko has not: column-width. :)
I'd like to add this information (the number of Firefox-supported
properties that Stylo has not implemented yet) to my project burndown
chart, along
On 26/08/16 15:11, Brian Anderson wrote:
> There are many benefits to this approach. Advancing Rust crypto is
> perennially a high-priority strategic nice-to-have in Rust, but so far we
> have not been able to find the right motivation to put weight behind it.
> Any time there is a glimmer of oppor
On Mon, Aug 29, 2016 at 2:23 PM, Chris Peterson wrote:
> Stylo has implemented exactly one property Gecko has not: column-width.
Oh, that's because Firefox implements it as -moz-column-width. I
haven't tried merging the prefixes -- this information can be scraped
from MDN, but it's only an issue
Hi,
just want to point that using independent Rust libraries may be good to avoid
problems like this: https://github.com/sfackler/rust-openssl/issues/255
Adelar
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/de
I included the Alexa numbers (these are not exactly accurate because
heycam's list counts property-value pairs, not properties, I need to write
a better script for extracting these correctly).
I also added a dashboard thingy that shows all the useful property counts
in the corner.
-Manish Goregao
This is awesome, thanks Manish!
Given our focus on testing, at this stage I think the most useful
prioritization would be reftests. We could turn on logging for
unimplemented properties (and properties values), and then see which ones
are the most common on one of shing's reftest runs.
On Mon, Au
6 matches
Mail list logo
