Over the weekend, Remy Sharp asked…
The concern here is that if you have a custom element named In the ES
Nathan Knowler suggested that Web Component authors could export just the Web Component class, without the Users could then define the custom element to use for themselves…
From my perspective, I don't think naming collisions are a concern. Web Components are HTML-driven, and specifically focused on DOM manipulation. If you have two custom elements with the same name, you're doing it wrong. I also think user-defined custom elements miss the mark on what makes Web Components so great. Because again, Web Components are HTML-driven. Being able to drop a JS file into my site and then do everything via HTML is what makes them so great. The second I have to It's a really good solution to a problem that I personally don't think really exists. Cheers, Want to share this with others or read it later? View it in a browser. |
Related Post:
- The Biggest SEO Trends of 2021 [New Ebook]
- Don't Miss Out on The Bonus Sessions at eSummit
- SEJ Today: Ecommerce & Mcommerce Trends & Tips for Christmas 2020
- Nokia’s Digital Operations Center software wins Fierce Innovation Award
- صِرَاطَ الَّذِيْنَ اَنْعَمْتَ عَلَيْهِمْ ەۙ غَيْرِ الْمَغْضُوْبِ عَلَيْهِمْ وَلَا الضَّاۤلِّيْنَ Terjemahan
0 Komentar untuk "[Go Make Things] User-defined Web Components"