W3C home > Mailing lists > Public > www-style@w3.org > April 2016

Re: Summary of calc serialization discussion

From: Alan Stearns <stearns@adobe.com>
Date: Thu, 7 Apr 2016 14:05:03 +0000
To: Shane Stephens <shans@google.com>, CSS WG <www-style@w3.org>
Message-ID: <E5F2730F-C57E-40F3-ADD8-79F35DEC1D7E@adobe.com>
> From: Shane Stephens <shans@google.com>
> Date: Thursday, April 7, 2016 at 12:44 AM
> To: Alan Stearns <stearns@adobe.com>, CSS WG <www-style@w3.org>
> Subject: Re: Summary of calc serialization discussion
> What I'm wondering is whether what you want is an API to replace
> stylesheet parsing of *rules*, so you can extract value strings
> directly. I think that you could probably use the specified string
> approach for that but there's a thorny caveat in that you'd only
> be able to see the last *valid* value for each property in each
> rule, rather than everything that's there. So I think even here
> we're better to wait for a proper parser API.

I had a similar thought during the call (where Tab responded, “Mayyyybe”). Both editors and third-party debugging tools would want to show all the declarations, so it might be best to solve this case with the parsing API.


Received on Thursday, 7 April 2016 14:05:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:02 UTC