Use native CSS parsing

[AkeemMcLennon]

Hello @bitinn

I recently created a library similar to vdom-parser at https://github.com/AkeemMcLennon/dom2hscript

I noticed your version had bug where it failed to parse certain CSS properties that contained semicolons such a base64 encoded strings. This pull request uses the browser's native css parser to improve accuracy.

[AkeemMcLennon]

It looks like the Zuul build is complaining about a lack of sauce labs credentials, but the tests seem to pass otherwise

[bitinn]

I believe I have avoided using native style object due to some reasons (likely virtual-dom related), but can't recall it yet. Still, thx for providing a test case :)

[AkeemMcLennon]

@bitinn The unit test "'should parse bracket style attribute on node'" initially failed when I made the changes. However, changing el = doc.body.firstChild; to el = doc.getElementsByTagName('body')[0].firstChild; in the parser resolved the issue.

I suspect this may have been part of your initial rationale since that test seemed oddly specific.

[niksy]

This would be useful to have since it would solve the issue of not having any inline styles in IE8 (#7)

[bitinn]

@niksy yep I would like to work on this soon. though I am not sure we will ever get full support for IE8.

[niksy]

@bitinn I have some commits on my fork which normalize feature set for IE8 and for the project I’m currently working on vdom-parser works really great. I can submit PRs when you get time to work on this.

[bitinn]

I figure out why I didn't use CSS parser after merging this: phantomjs actually output differently from chrome. especially on inline input like background: url(path). Chrome will change it to url("path") while phantomjs, without proper DOMParser support, return url(path).

Since this is intended for browser anyway, I will workaround the phantomjs issue...

[bitinn]

https://travis-ci.org/bitinn/vdom-parser/builds/117241478

Things are a lot worse than I remembered, Safari doesn't agree with Chrome. So we either generate additional patches for Safari (including iOS) or for Chrome (including android) using CSS parser.

Maybe I have to back out of this...

[bitinn]

landed in v1.3.0