On 11/29/17 12:03 PM, Ting-Yu Lin wrote:
We can ship all the properties in this module at once, or we could probably
divide it into two stages, and ship it to the user incrementally.
For example, stage 1 is to ship shape-outside" (except <Image> value) and
"shape-margin", and stage 2 is to ship the remaining "shape-outside:
<image>" and "shape-image-threshold". If everything goes well, stage 1 is
targeting at Firefox 59.
I think supporting only a subset of the valid values for a property
is problematic.
CSS conformance rules says:
"[...] the user agent must parse the value according to the property
definition. This means that the user agent must accept all valid values
and must ignore declarations with invalid values."
https://www.w3.org/TR/CSS21/conform.html
Shipping support for a subset of the properties in a spec might make sense
in some cases, but since you say:
The downside of the two-stage roll-out could raise web-compat issues
because Blink and Webkit already support the entire module.
it's not probably not a good idea in this case, for web-compat reasons.
/Mats
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
