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
I know a lot of care has been made to ensure the specificity is (0, 1, 0) everywhere, but is this an exception to that?
If it is not, and I suspect not, then I think it would make sense to move the sizing class from rt-Container to rt-ContainerInner. This is the only place in the code base where rt-r-size is used in a "compound" (?) selector statement.
The following code snippet does not work:
The result is that the parent container's size overrides the child:
Duplicate #591
The text was updated successfully, but these errors were encountered: