- From: Marcos Caceres <w3c@marcosc.com>
- Date: Sat, 2 Feb 2013 14:19:20 +0000
- To: Brian Kardell <bkardell@gmail.com>
- Cc: François REMY <francois.remy.dev@outlook.com>, "public-nextweb@w3.org" <public-nextweb@w3.org>
On Saturday, 2 February 2013 at 13:48, Brian Kardell wrote: > > On Jan 26, 2013 5:57 AM, "François REMY" <francois.remy.dev@outlook.com (mailto:francois.remy.dev@outlook.com)> wrote: > > > > I believe we should have this discussion with Tab Atkins. One of his focuses this year will be CSS polyfills, I'm sure he'll need to craft some OM for this; since he already made its own CSS parser in JS, he'll probably look forward extending it. > > > > François > > > Group (+tab) > I've shared an illustration of the output of Tab's parser https://raw.github.com/bkardell/css-parser/master/docs/parser-info.html . Version served with correct mime type: https://rawgithub.com/bkardell/css-parser/master/docs/parser-info.html > The only thing that is slightly misleading/confusing is that this is the json serialization which isn't exactly the same as the object you get from parse. In reality, we could use either/or. I'd like to propose that this is probably the best and most complete parser for anything compatible with the syntax. We should be able to easily extend this for slightly easier consumption or run it through transforms if it doesn't exactly match our requirements. > > Brian Kardell :: @briankardell :: hitchjs.com (http://hitchjs.com)
Received on Saturday, 2 February 2013 14:19:51 UTC