@igalia@bkardell@Meyerweb@mia are we ever going to have a sandboxed shadow dom which also can run independent JS, not only css? There are too many use cases for iframes and we should probably kill them eventually?
@matthewp@igalia@Meyerweb@mia What's not new? Shadow DOM? Most people haven't spent much time with it and the state of it is constantly evolving just a little, so it doesn't matter that it's been around since then -- or even that it was in XBL, or arguably before that in SVG in the late 90s
@bkardell@igalia@Meyerweb@mia The state of everything is constantly evolving. Shadow DOM, as an end-user spec, has been around longer than CSS grid. But we're still talking about it like it's 2013. It's not. No one does this for Grid or any other technology.
We need to stop having first-principles conversations about this topic, we have 10+ years of history and exploration that I think spec people are either ignoring or not aware of, either case is troubling.
I just want to note the "we" I am talking about is the global mass of developers. Take note of how many posts there have been in the past 6 months discovering web components. The 2013 v0 didn't gain adoption. We finally got to something close to the state of today shipping in all browsers in 2020, still minus some major parts like declarative shadow dom which like, just shipped in FF
@igalia@Meyerweb@mia If you're too young to get the reference, I'm happy to be able to introduce you to this classic song (which predates my life even)...
Add comment