@claviska The "Why Not Use Unique Event Names?" part is spot on! Our defaults align with your understanding that arbitrarily added weirdness/uniqueness for the sake of uniqueness has no place in the web platform.
@claviska We love using https://t.co/63lfF4EYuH.constructor === PDFFileElement
But also offer our users an attribute on our embedding script element itself:
With <script event-name-prefix=type โฏ>, each embedded custom element fires events prefixed by its own type (=tag name).
@MicrosoftEdge@MSEdgeDev@MozDevNet@samsunginternet โ can you please join the party in keeping https://t.co/8Eso9gK5dp up-to-date? This is essential for various tools and services, such as our own https://t.co/NV0SDYIQHK (we are still performing manual updates just for @samsunginternet)
๊ฐ์ฌํฉ๋๋ค!
@LinuxSeb We are building a no-reload HTML(/CSS/JS) playground with instant editor โ output sync โ to make the world a better place!
You can read how we differ from the likes of CodePen here: https://t.co/2i2Y5pZ8S8