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'm requesting a TAG review of CSS Overflow for replaced elements.
This feature allows developers to use the existing overflow property with replaced elements that paint outside the content-box. Paired with object-view-box this can be used to create an image with a custom glow or shadow applied, with proper ink-overflow behavior like a CSS shadow would have.
Tests: WPTs are being added as part of implementation in Chromium.
User research: N/A
Security and Privacy self-review²: N/A. This change implements an existing CSS feature for replaced elements and doesn't introduce any new security/privacy concerns. One concern worth highlighting is allowing an iframe to generate ink overflow that can occlude content on the embedding frame. For this reason, a UA stylesheet enforces the overflow value to be clip for iframe, embed, object. See discussion here.
GitHub repo (if you prefer feedback filed there): N/A
Primary contacts (and their relationship to the specification):
Wotcher TAG!
I'm requesting a TAG review of CSS Overflow for replaced elements.
This feature allows developers to use the existing
overflow
property with replaced elements that paint outside the content-box. Paired withobject-view-box
this can be used to create an image with a custom glow or shadow applied, with proper ink-overflow behavior like a CSS shadow would have.overflow
value to beclip
for iframe, embed, object. See discussion here.Further details:
We'd prefer the TAG provide feedback as (please delete all but the desired option):
💬 leave review feedback as a comment in this issue and @-notify [github usernames]
The text was updated successfully, but these errors were encountered: