-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Needs client side polyfill #2
Comments
I've made a little parser in JavaScript. It's not finished yet. EDIT: Updating to 1.1.0, now it can export DOMDocument. It's just a parser but it can be used:
|
Looks really cool. Hope to see more :) |
But before html6-html5 convertor, we need a CSS parser. And maybe a JS framework. |
Why do we need a CSS parser? CSS works fine with XML. And why a whole framework? |
OK, we can use xhtml with both
Oh and also there's a problem with programmatically creating elements with ns prefix. That's impossible! This comment was editted 5 times. |
CSS selectors need to be general and work across XML. CSS doesn't have predefined elements you can select for example. You can style those elements fine right now: http://jsbin.com/iCuDEYE/2/edit The only thing I can think of is adding 1 selector to make The JS thing should just be part of the polyfill. |
I don't mean creating a new spec - our problem is that all And the second problem with css is that Do you understand? EDIT: Oops, to fast reading. I thought you said that CSS works across all the XML. My fault, correcting the comment. |
I've just found an alternative way
Pros:
Cons:
|
After a short break (not even a year), I've got a new update! |
No description provided.
The text was updated successfully, but these errors were encountered: