Intent to implement: CSS Houdini - Properties & Values API Level 1

[Jonathan Chan]

Summary:

Allow web developers to register typed and animatable custom CSS properties through JavaScript with configurable inheritance and initial values.

Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1273706
Link to standard: https://drafts.css-houdini.org/css-properties-values-api/
Platform coverage: all platforms
Estimated or target release: This will likely be available, preffed off, in Firefox 51. Release date (for the pref-flip) unclear -- may depend on our implementation timeline for other Houdini specs.
Preference behind which this will be implemented: layout.css.properties_and_values.enabled
DevTools bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1287171

Jonathan Chan

[Ms2ger]

Hey Jonathan,

Do we know how other vendors feel about this?

Are there automated tests that will be shared with other vendors (and
Servo)?

Thanks
Ms2ger

[Daniel Holbert]

On 07/25/2016 07:11 AM, Ms2ger wrote:
> Hey Jonathan,
[...]

> Do we know how other vendors feel about this?

Sentiment seems to be positive.

Browser vendors are collaborating on developing the Houdini specs, and I
haven't heard any serious reservations on this spec. (This is among the
more simple/stable of the Houdini family of specs.)

I believe we're not the only ones working on an implementation, too --
Google has a work-in-progress implementation of the Houdini "CSS Paint"
API (with a brief demo video here [1]), and that API layers on top of
this feature ("css properties & values"), which I think means they're
also working on implementing this feature.

> Are there automated tests that will be shared with other vendors (and
> Servo)?

There are some reftests on the bug [2] (final patch).

~Daniel

[1] https://www.youtube.com/watch?v=AfiaReDetZE
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1273706

[James Graham]

On 25/07/16 16:48, Daniel Holbert wrote:
> On 07/25/2016 07:11 AM, Ms2ger wrote:
>> Hey Jonathan,
> [...]

>> Do we know how other vendors feel about this?
>

> Sentiment seems to be positive.
>
> Browser vendors are collaborating on developing the Houdini specs, and I
> haven't heard any serious reservations on this spec. (This is among the
> more simple/stable of the Houdini family of specs.)
>
> I believe we're not the only ones working on an implementation, too --
> Google has a work-in-progress implementation of the Houdini "CSS Paint"
> API (with a brief demo video here [1]), and that API layers on top of
> this feature ("css properties & values"), which I think means they're
> also working on implementing this feature.
>

>> Are there automated tests that will be shared with other vendors (and
>> Servo)?
>

> There are some reftests on the bug [2] (final patch).

AIUI if you move those tests to somewhere under
layout/reftests/w3c-css/submitted then dbaron will upstream them to the
CSSWG testsuite at some point.

Alternatively I have no qualms about putting them in web-platform-tests
where there are fewer metadata requirements and they will certainly be
shared, but CSSWG might grumble at you.

Either way we should put them somewhere where it is possible for other
vendors to check for interoperability.

[Jonathan Chan]

> On Jul 25, 2016, at 10:47 AM, James Graham <ja...@hoppipolla.co.uk> wrote:
>
> On 25/07/16 16:48, Daniel Holbert wrote:
>> On 07/25/2016 07:11 AM, Ms2ger wrote:

>>> Are there automated tests that will be shared with other vendors (and
>>> Servo)?
>>

>> There are some reftests on the bug [2] (final patch).
>
> AIUI if you move those tests to somewhere under layout/reftests/w3c-css/submitted then dbaron will upstream them to the CSSWG testsuite at some point.
>
> Alternatively I have no qualms about putting them in web-platform-tests where there are fewer metadata requirements and they will certainly be shared, but CSSWG might grumble at you.
>
> Either way we should put them somewhere where it is possible for other vendors to check for interoperability.

Alright, thanks. I have a preliminary Mochitest that I'll port to a Web Platform Test. That tests more functionality than the reftests I've included and would be better for sharing, I think.

Thanks.

Jonathan

[Ehsan Akhgari]

On 2016-07-22 5:26 PM, Jonathan Chan wrote:
> Summary:
>
> Allow web developers to register typed and animatable custom CSS properties through JavaScript with configurable inheritance and initial values.
>
> Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1273706
> Link to standard: https://drafts.css-houdini.org/css-properties-values-api/
> Platform coverage: all platforms
> Estimated or target release: This will likely be available, preffed off, in Firefox 51. Release date (for the pref-flip) unclear -- may depend on our implementation timeline for other Houdini specs.
> Preference behind which this will be implemented: layout.css.properties_and_values.enabled
> DevTools bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1287171

Hi Jonathan,

Does this interact with Stylo by any chance? If the answer is yes, is
anyone planning to implement this in Servo at the same time?

Thanks,
Ehsan

[Jonathan Chan]

Hi Ehsan,

On Jul 26, 2016 5:58 AM, "Ehsan Akhgari" <ehsan....@gmail.com> wrote:
> Does this interact with Stylo by any chance?

I understand that pending the completion of Stylo, this implementation will
be replaced by a Servo implementation. I don't believe this should
otherwise interact -- I had to modify nsRuleNode a little to accomodate
uninherited variables & a new style struct but I don't think that affects
Stylo (?).

> If the answer is yes, is
> anyone planning to implement this in Servo at the same time?

I am currently working on implementing the spec in Servo too!

Thanks!

Best regards,
Jonathan