-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Turn into a web component #344
Comments
I'd have to look into this in more detail as I've not done a lot with components yet (but would like to) 👍 |
I want to resurface this as components have grown in the last two years. +1. |
I've actually been thinking about this a lot. Would there be an easy way for people to polyfill support for web components? How about Stencil ? |
I believe all of the evergreen browsers support the standards now. Really custom elements are the most important piece, and there are lightweight polyfills for that API. I recommend looking into LitElement or just lit-html plus custom elements as a very lightweight solution to this problem |
@lastmjs Can you share a link. I'm using lit-element and trying to fit this into my component but can't work out the issues. |
Sorry, what would you like a link to? |
I thought you had some solution to bring this into a LitElement component. If that is the case, I would like a link to that. If not, could you expand upon what you meant in that first comment of yesterday? In particular, you recommended looking into LitElement as a lightweight solution to "this problem", which I took to mean using plyr in a component. I am using LitElement, but cannot figure out how to get plyr working in a component within the framework. |
Oh I see. No, I do not have a solution for using plyr in a web component. I actually don't use this project anymore, I'm just trying to give some advice. The original issue was to encourage plyr itself to be a web component. I was encouraging the maintainers to implement plyr with LitElement or lit-html, which would hopefully make using plyr within your own web component or other applications simpler |
It would be great if the library were turned into a web component. That would encapsulate and simplify initialization, and would work across all frameworks and browsers that support the web components standards or polyfills.
The text was updated successfully, but these errors were encountered: