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 is a follow up to #626 which introduced object-overflow to support the same functionality. Based on feedback in the CSSWG the proposal has been updated to use the existing overflow property. This property is already respected for svg elements and the proposal aims to have consistent behaviour for all replaced elements.
The text was updated successfully, but these errors were encountered:
This seems reasonable; I think we could call this "worth prototyping", for the same reasons discussed in #626.
(This is the same feature that was discussed there in #626, though it's been morphed to have slightly different ergonomics to avoid creating near-duplicate feature sets that apply to different elements.)
Request for Mozilla Position on CSS Overflow for replaced elements
object-overflow
andobject-view-box
interact withoverflow
andoverflow-clip-margin
? w3c/csswg-drafts#7144 for specific edits to this spec.Other information
This is a follow up to #626 which introduced object-overflow to support the same functionality. Based on feedback in the CSSWG the proposal has been updated to use the existing
overflow
property. This property is already respected for svg elements and the proposal aims to have consistent behaviour for all replaced elements.The text was updated successfully, but these errors were encountered: