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
After soe changes, due to ambiguities with the place-self and place-items shorthands, it was decided to restrict the position of the overflow-alignment values. That's fine. However, I'm not sure the current syntax for the justify-items is the one we were looking for:
| normal | stretch | <baseline-position> | [ <overflow-position>? <self-position> ] | [ legacy || [ left | right | center ] ]
If I understood it correctly, the syntax above parses as invalid CSS declarations like 'overflow leff'. As a matter of fact, overflow-positions is only valid if used with a self-position. However, the justify-self syntax parses as valid the combination with 'left' and 'right' as well.
Is this the intended behavior ?
The text was updated successfully, but these errors were encountered:
Umm, the new proposed syntax allows "legacy safe left" and "unsafe right legacy" . Are we sure we want overflow-position in combination with 'legacy ? According to the specs, the 'legacy' keyword exists to implement the legacy alignment behavior of HTML’s <center> element and align attribute, so I don't think the overflow-position makes sense there.
After soe changes, due to ambiguities with the place-self and place-items shorthands, it was decided to restrict the position of the overflow-alignment values. That's fine. However, I'm not sure the current syntax for the justify-items is the one we were looking for:
https://drafts.csswg.org/css-align-3/#propdef-justify-items
If I understood it correctly, the syntax above parses as invalid CSS declarations like 'overflow leff'. As a matter of fact, overflow-positions is only valid if used with a self-position. However, the justify-self syntax parses as valid the combination with 'left' and 'right' as well.
Is this the intended behavior ?
The text was updated successfully, but these errors were encountered: