- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Tue, 23 Dec 2014 09:04:25 -0800
- To: "L. David Baron" <dbaron@dbaron.org>
- Cc: Alan Stearns <stearns@adobe.com>, "daniel.glazman@disruptive-innovations.com" <daniel.glazman@disruptive-innovations.com>, "public-wtf@w3.org" <public-wtf@w3.org>
On Tue, Dec 23, 2014 at 8:02 AM, L. David Baron <dbaron@dbaron.org> wrote: > On Tuesday 2014-12-23 15:56 +0000, Alan Stearns wrote: >> On 12/23/14, 6:58 AM, "L. David Baron" <dbaron@dbaron.org> wrote: >> >> >On Tuesday 2014-12-23 08:57 +0100, Daniel Glazman wrote: >> >> 5. access to unknown properties and values >> > >> >> 7. add a new property to the parser, to allow layout experiments through >> >> the box tree >> > >> >Some previous discussions on items 5 and 7: >> > >> >http://lists.w3.org/Archives/Public/www-style/2012Aug/thread.html#msg169 >> >https://bugzilla.mozilla.org/show_bug.cgi?id=188321 (esp. comment 14) >> >https://www.w3.org/Bugs/Public/show_bug.cgi?id=14203 >> >> Are 5 and 7 required for arbitrary properties? I’ve assuming that custom >> properties would be sufficient. > > Custom properties probably aren't sufficient to simulate > non-inherited properties. > > They also probably aren't sufficient to simulate error handling > (which requires discarding invalid values and falling back to the > next value in the cascade). Correct on both counts. As we move to expose more custom things, I plan to upgrade Custom Properties as well - they're currently highly specialized for the Variables use-case. In particular, I plan to allow you to specify some parameters for the property - initial value, inherited, maybe even a simple grammar, which allows both error-checking and animation to work automatically. ~TJ
Received on Tuesday, 23 December 2014 17:05:16 UTC