- From: sky2 <notifications@github.com>
- Date: Tue, 16 Feb 2021 14:36:20 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/579/780161940@github.com>
On Mon, Feb 15, 2021 at 4:33 PM Peter Linss <notifications@github.com> wrote: > Looked at this today with @hober <https://github.com/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? > > As the "overflow: hidden" case is still scrollable (programatically), I don't think it makes sense to support the overflow-clip-margin there. > > 1. > 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. > > If we were to introduce another property, then we would end up contradicting configurations. For example, 'overflow: scroll;' and 'scrollable: false' ? -Scott > > 1. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/w3ctag/design-reviews/issues/579#issuecomment-779510583>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ACHE7YRVEQSG7V5BO5NH553S7G4OZANCNFSM4ULE44UA> > . > -- 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-780161940
Received on Tuesday, 16 February 2021 22:36:33 UTC