Re: [w3ctag/design-reviews] CSS overflow: clip and overflow-clip-margin (#579)

Looked at this today with @hober and have two points of feedback:

1) It seems odd to constrain the overflow-clip-margin to the `overflow: clip` case. Wouldn't an additional margin also make sense in the `overflow: hidden` state?

2) Adding another high-level feature that has the same behavior as another high-level feature with the exception of a low-level detail seems like an anti-pattern that CSS is guilty of in multiple places. Examples are other properties that cause the generation of stacking contexts or containing blocks, and are often used just for those side-effects (e.g. `position: relative` with no offsets). Many of these cases would be better served by a direct control of the lower-level feature, e.g. "make this a stacking context", or "make this a containing block". We're wondering if it doesn't make more sense to have an individual control of whether something is a scroll container and use that feature in conjunction with `overflow: hidden` to get the `overflow: clip` behavior.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/579#issuecomment-779510583