Jonathan Kingston

@yoavweiss I read that in another post somewhere. My initial worry was does that scale if every element was 'special'. However that certainly does simplify the problem.

Heh yeah that's why I wasn't calling it special. I'm thinking of every web component able to have this behaviour if it chose. In my templates instead of writing html...

@PaulSpr that's a great question and I have seen the feature mentioned as an iframe. This is similar to the behaviour of shadow dom. This is how I was thinking...

@jehoshua02 I'm a fail hard sort of programmer too but user agents could not just crash though so some error handling would have to happen. Also it would allow third...

@tabatkins I fear an example like this would come along. Does my other comment around this feature being more than just a special case cause issues? My other comment around...

The main use case for me as I said in #9 is: Having element queries for a web components allows components to be self contained. I think that with this...

Worth taking advantage of element's having the ability to nest? With implied `@nest` from: http://discourse.specifiction.org/t/css-nesting-specification/839/29 ``` .element { @container ( min-width: 60rem ) { .child-el { background-color: blue; } }...

@aFarkas exactly that syntax is what I was thinking thanks.

Right the web platform already has [SRI](https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity) and the capability to add them to imports, this would solve the cache invalidation turtles all the way down that @mozfreddyb and @fmarier...

Whilst decoupling this idea from import maps seems worthwhile to improve traction. My hunch is the engineering effort to implement this would be pretty significant and not too dissimilar to...