Even at only v1, along with the "don't break the web" mentality, Web Components are an extremely important stepping stone. We should cheer the implementers of these proposal on and help!
We can now render whatever content we want confidently, inside of other apps. Less than an iframe, but enough isolation (or not if you want) with all of the important benefits of being baked into the current document.
I've tested https://kherrick.github.io/sprite-garden/ by pressing, "W", "↑", or "space bar" to get started moving in the game. Afterwards the other functionality seems to work as expected in Firefox on Linux with the following versions:
- 140.3.1esr (64-bit)
- 143.0.4 (64-bit)
- 145.0a1 (2025-10-02) (64-bit)
Are you able to describe what issue you are seeing in particular?
XSLT currently provides a lot of value, as the browser can use it to transform documents directly, and it is exposed to JavaScript for scripting. Exploring it recently, including creating a PWA with XML sources reminded me why I like developing on the web. It made me think--RSS feeds can be PWA's now--right?
It seems like XSLT 3.0 would open up a lot of new opportunities and patterns, especially if it continues to work with existing standards, as the current version does. The Web Platform is so cool.
> I wish there were more work done in the area of composable GUIs, where the core logic of applications is scriptable and where these elements can be combined in ways that could be even more expressive than Unix pipes are. Every now and then I have thoughts about taking a modern Smalltalk implementation and writing a suite of composable GUI apps as a demonstration of this idea.
We can now render whatever content we want confidently, inside of other apps. Less than an iframe, but enough isolation (or not if you want) with all of the important benefits of being baked into the current document.
Example: https://kherrick.github.io/block-garden/
Same custom element running inside Angular: https://kherrick.github.io/apps/playground/block-garden