Skip to content
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

Track Custom Element rewrite changes #56

Closed
tbranyen opened this issue Mar 2, 2016 · 3 comments
Closed

Track Custom Element rewrite changes #56

tbranyen opened this issue Mar 2, 2016 · 3 comments

Comments

@tbranyen
Copy link
Owner

tbranyen commented Mar 2, 2016

Reference: WICG/webcomponents#405

Since the Custom Element API is still in flux, I've only implemented the API that matches current browsers. I'll be starting on an opt-in to try out the new API. I'm thinking something like diff.enableExperimental() which matches enableProllyfill() except brings in the new APIs and will change with the leading browser implementation.

@tbranyen tbranyen changed the title Track Web Component rewrite changes Track Custom Element rewrite changes Mar 2, 2016
@tbranyen
Copy link
Owner Author

So much has changed since then... it's gotten a rewrite since the last rewrite. It's out of control so I'm going to rip out of this library until it stabilizes.

@jamesplease
Copy link

slight preference for:

enableProllyfill({experimental: true}); if this ever comes to be

@tbranyen
Copy link
Owner Author

Closing this out, since I'm going to leave it to the browser vendors to settle on a standard and then we'll revisit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants