Re: [css-houdini-drafts] Consider supporting existing CSS Property parsings

Hi there!

I discovered by chance that as part of [the big post-F2F 
rewrite](https://github.com/w3c/css-houdini-drafts/commit/653248c38d08f9f9e8287a00738085c366f6b78e),
 this feature had been removed.

According to [the F2F 
notes](https://lists.w3.org/Archives/Public/public-houdini/2016Feb/0004.html),
 this is based on feedback from Apple that a list of things would be 
somewhat easier for them to implement than to reuse what native 
properties already support. I guess that every browser will find it 
easier or harder to support either of which, though, and not 
necessarily the same one. 

```
  shane: To go back... want to ask one question about issue #99
  shane: Specifically, dino and smfr, which is better for you?
         Better to have a list of things or to reference property
         names?
  smfr: I prefer explicit list; referencing properties is harder for
        us.
```

I didn't spot that discussion during last f2f, but the outcome makes 
me a bit sad. If people still feel this is the way forward for a 
faster L1 (ping @smfr), I guess I can live with that, but could we 
agree on this being a desired L2 feature, at the very least? This 
would enable every single thing expressible in css to be also 
expressible and animatable for custom properties (shapes, clip rects, 
background-position, etc...) which is something I'm really looking 
forward to. 

Any opinion?

-- 
GitHub Notification of comment by FremyCompany
Please view or discuss this issue at 
https://github.com/w3c/css-houdini-drafts/issues/48#issuecomment-238717960
 using your GitHub account

Received on Tuesday, 9 August 2016 22:58:33 UTC