- From: Divya Manian <manian@adobe.com>
- Date: Wed, 13 Jun 2012 16:54:38 -0700
- To: "L. David Baron" <dbaron@dbaron.org>, Chris Eppstein <chris@eppsteins.net>
- CC: "www-style@w3.org" <www-style@w3.org>
On 6/13/12 4:44 PM, "L. David Baron" <dbaron@dbaron.org> wrote: >On Wednesday 2012-06-13 16:17 -0700, Chris Eppstein wrote: >> If it really is a property then make it a property with a -user- prefix >>and >> then make all properties accessible for read. > >That would make declarations of all CSS properties consume more >memory and take more time to parse, since we'd have to store a token >stream in addition to the other parsing that needs to happen. Then I propose we actually make it a separate definition instead of overloading a property definition. I have been down this path several times in my career as a web developer to know that "same same, just one small thing different" is a recipe for disaster in the future. I assert CSS variables will have a greater role to play in the future which will be overly constrained if we make it a slightly different 'property'.
Received on Wednesday, 13 June 2012 23:55:12 UTC