-
Notifications
You must be signed in to change notification settings - Fork 73
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
Add support for Custom Elements #68
Comments
Any comment? Is that something you would consider addressing? Thanks! |
Yeah, I think this is definitely a reasonable thing to add! If you're interested in taking a stab at it, it should just be a small change to https://github.com/Prismatic/dommy/blob/master/src/dommy/template.cljs#L32-L34 |
Great, I'll take a look then. |
Actually yes I would be interested in creating a separate project that would be based on the templating code and add some more features on top of it. |
Definitely! Let me know if you need any help getting started. |
Great! I'll let you know how it goes. |
I pushed a first release that just bundle dommy templating code. Let me know if something looks incorrect. |
@jeluard That's giving me a 404. Might it be a private repo? |
Oups it should be public now. |
I am curious to know why there was 2 versions of |
I think the function version was dead code that wasn't ever removed after the introduction of |
Custom Elements is a new w3c specification that introduces a new API to create DOM element: document.createElement(localName, typeExtension). This API reflects a new html syntax
<button is="my-button"></button>
wherebutton
would be the localName andmy-button
the typeExtension.The equivalent hiccup syntax
[:button {:is "my-button"}]
should generate the proper DOM call when used withdommy
to support this spec as settingis
as an attribute (current behavior) has no effect.The text was updated successfully, but these errors were encountered: