- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Aug 2018 16:48:56 +0000
- To: public-css-archive@w3.org
The Working Group just discussed `fully specify the "Overflow and Scroll Positions" section`. <details><summary>The full IRC log of that discussion</summary> <dael> Topic: fully specify the "Overflow and Scroll Positions" section<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/1425#issuecomment-411930443<br> <dael> astearns: Edits have been made.<br> <dael> fantasai: Wanted to call attention to things tryign to fix<br> <fantasai> https://drafts.csswg.org/css-align/#overflow-scroll-position<br> <dael> fantasai: This section is about when you have a scroll container and it has align content so you center all the content in the box in the box. When you have a scroll container we decided that rather then ignore alignment or align content to the end and overflow to the top we wanted to make it so you could read the content and be able to scroll to it. That meant moving content down and show as if end aligned<br> <dael> TabAtkins: Almost same as aligning scroll thumb in scroll track. Not quite same. Some content alignments b/c way some browsers discard padding means it would normally be impossible to achieve same layout wither if overflow:scroll or not.<br> <dael> TabAtkins: Have a bit about mandating you provide enough padding to match. Also helps solve issue that people want block-end and inline padding. We say if you use can content alignment you get the padding. That makes all padding work as expected.<br> <dael> florian: Does that solve the legacy or do we have too many legacy behaviors?<br> <dael> TabAtkins: Still not sure what legacy should be. Lets us have t he good behavior so we can solve legacy separately<br> <dael> florian: Fair enough<br> <dael> astearns: dbaron You've been i this issue, have you looked at latest edits?<br> <dael> dbaron: I don't think so<br> <dael> astearns: Leave this as please everyone take a look and we come back next week t o resolve?<br> <dael> TabAtkins: yeah<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1425#issuecomment-413259977 using your GitHub account
Received on Wednesday, 15 August 2018 16:48:57 UTC