You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This implies you might want to use normalalong side either size or inline-size. The only reason to do that would be if inline-size acted as an override to the normal behavior - in which case authors would need to re-assert normal inline-size as a way to query both styles and sizes of the container. But as far as I can tell, that's not the behavior described in the spec, or the desired behavior, or the way things work with the Chrome prototype of style queries. Instead, a container type of inline-size normalbehaves the same as a container type of inline-size.
I think we should probably change the syntax to:
normal | size | inline-size
But, alternately, we could just add a note to clarify how this works.
The text was updated successfully, but these errors were encountered:
Currently, the formal syntax for
container-type
is:This implies you might want to use
normal
along side eithersize
orinline-size
. The only reason to do that would be ifinline-size
acted as an override to thenormal
behavior - in which case authors would need to re-assertnormal inline-size
as a way to query both styles and sizes of the container. But as far as I can tell, that's not the behavior described in the spec, or the desired behavior, or the way things work with the Chrome prototype of style queries. Instead, a container type ofinline-size normal
behaves the same as a container type ofinline-size
.I think we should probably change the syntax to:
But, alternately, we could just add a note to clarify how this works.
The text was updated successfully, but these errors were encountered: