[css-contain] Stacking Context is undesired

[FirstVertex]

https://www.w3.org/TR/css-contain-3/

@container queries create a new stacking context. This is 100% undesired. Media queries do not work like that. All my z-index are fubar after trying to use @container queries. There is no logical relationship between the container size (dimensions) and the stacking order (z-index). Marking an element as a container should not ever influence the stacking context. Css @container queries are useless in their current state because of this extra stacking context which adds nothing but extra problems and quirks. Please delete the part of container queries which makes a new stacking context so that container queries can actually be used.

See Also
https://stackoverflow.com/questions/76607899/why-does-container-type-inline-size-seem-to-mess-with-stacking-overflow-rules

https://stackoverflow.com/questions/76237217/how-can-i-position-z-indexed-contained-within-css-containers-used-for-container

[mirisuzanne]

I believe this has been fixed by #10544 - and appears to behave correctly in recent versions of Chrome and Firefox (looks like I need an upgrade to test the latest Safari):

See https://codepen.io/miriamsuzanne/pen/pvoyNOE