- From: L. David Baron <dbaron@dbaron.org>
- Date: Mon, 19 Oct 2015 11:16:42 -0700
- To: Robert Hogan <robhogan@gmail.com>
- Cc: www-style@w3.org
- Message-ID: <20151019181642.GA32198@pescadero.dbaron.org>
On Monday 2015-10-19 18:10 +0000, Robert Hogan wrote: > HI all, > > Could I get some direction on this? Is the exclusion of tables from > overflow-x and overflow-y by confining them to block-containers deliberate? Not sure what the original intention was, but I wasn't aware of any implementations applying them to tables. Do they? -David > Maybe I'm just being dumb and overflow-x and overflow-y can apply safely to > the 'table wrapper box', it's just the table box inside it that's excluded > by the language 'In CSS 2.2, a block-level box is also a block container > box unless it is a table box or the principal box of a replaced element.' > > It's hard to tell what the intention is and I'd like to make Blink do the > right thing here. > > Thanks, > Robert > > > > On Wed, Jul 22, 2015 at 6:58 PM Robert Hogan <robhogan@gmail.com> wrote: > > > Hi there, > > > > Per https://drafts.csswg.org/css-overflow-3/#overflow-properties > > overflow, overflow-x and overflow-y only apply to block containers in > > CSS2 land. To me, this means that the resolution of conflicting > > overflow-x and overflow-y values is either undefined or UAs shouldn't > > allow overflow-x/overflow-y to be specified for tables in the first > > place. It looks like everyone does allow the latter so is the next > > best step to define in css-overflow the resolution everyone currently > > uses in practice, which is to resolve 'hidden' to 'visible' if x and y > > conflict? > > > > Thanks, > > Robert > > -- 𝄞 L. David Baron http://dbaron.org/ 𝄂 𝄢 Mozilla https://www.mozilla.org/ 𝄂 Before I built a wall I'd ask to know What I was walling in or walling out, And to whom I was like to give offense. - Robert Frost, Mending Wall (1914)
Received on Monday, 19 October 2015 18:17:10 UTC