- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Mar 2024 16:51:27 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-align-3] Default safety of scroll containers`, and agreed to the following: * `RESOLVED: all scroll containers default to unsafe alignment (not actually unsafe on scroll container)` <details><summary>The full IRC log of that discussion</summary> <keithamus> fantasai: previous issue; when we have alingment applied to block, if the content is bigger than box it overflows. For flex/grid containers we overflow in whatever direction<br> <keithamus> fantasai: we can specify to always overflow to end of container, so not clipped by scrollbars<br> <keithamus> fantasai: content alignment on block containers we decided to do safe alignment by default. reduce compat impact.<br> <keithamus> fantasai: block container thats scroll container has no safety concerns around accidental clip because ... it'll overflow<br> <keithamus> fantasai: if I set align-content: end on scroll container should it end align content so you scroll to end of the content? Or should we layout same way a non-scroll or block container where its aligned to start and overflows toward ends<br> <fantasai> https://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A%3Cdiv%20style%3D%22align-content%3A%20end%22%3E%0A%20%20Line%201%3Cbr%3ELine%202%3C%2Fdiv%3E%0A%3Cdiv%20style%3D%22align-content%3A%20end%22%3E%0A%20%20Line%201%3Cbr%3ELine%202%3Cbr%3ELine%203%3Cbr%3ELine%204%3Cbr%3ELine%205%3C%2Fdiv%3E%0A%3Cdiv%20style%3D%22align-content%3A%20end%3B%20overflow%3A%20auto%22%3E%0A%20%20Line%201%3<br> <keithamus> fantasai: made demo<br> <fantasai> Cbr%3ELine%202%3Cbr%3ELine%203%3Cbr%3ELine%204%3Cbr%3ELine%205%3C%2Fdiv%3E%0A%3Cdiv%20style%3D%22align-content%3A%20unsafe%20end%22%3E%0A%20%20Line%201%3Cbr%3ELine%202%3Cbr%3ELine%203%3Cbr%3ELine%204%3Cbr%3ELine%205%3C%2Fdiv%3E%0A%3Cdiv%20style%3D%22align-content%3A%20unsafe%20end%3B%20overflow%3A%20auto%22%3E%0A%20%20Line%201%3Cbr%3ELine%202%3Cbr%3ELine%203%3Cbr%3ELine%204%3Cbr%3ELine%205%3C%2Fdiv%3E%0A%0A%<br> <fantasai> 3Cstyle%3E%0A%20%20body%20%7B%20display%3A%20flex%3B%20height%3A%205em%3B%20%7D%0A%20%20div%20%7B%20margin%3A%200.5em%3B%20border%3A%20solid%3B%20%7D%0A%20%20div%3Ahover%3A%3Abefore%20%7B%0A%20%20%20%20%20position%3A%20absolute%3B%0A%20%20%20%20%20top%3A%200%3B%20left%3A%200%3B%0A%20%20%20%20%20content%3A%20attr(style)%3B%0A%20%20%20%20%20background%3A%20Canvas%3B%0A%20%20%7D%0A%3Cstyle%3E<br> <fantasai> https://software.hixie.ch/utilities/js/live-dom-viewer/saved/12505<br> <keithamus> iank_: which side is scroll origin on in align end case?<br> <keithamus> fantasai: align-content: unsafe-end content will overflow to top and initial scroll position will scroll to bottom so you can scroll upward<br> <keithamus> iank_: so scroll origin at end<br> <keithamus> fantasai: so if I set align-content: end instead of unsafe-end do we want it like unsafe-end or layout like top aligned if content overflows<br> <keithamus> fantasai: thats what happens if you're not a scroll container<br> <keithamus> iank_: implications that safe-end scroll origin at top vs unsafe-end scroll origin at bottom<br> <keithamus> fantasai: right. what should default be?<br> <keithamus> fantasai: playing around I thought it was more convenient to say align-content; end makes scroll container end<br> <keithamus> fantasai: but can see consistency argument. to layout as non scrolling.<br> <keithamus> fantasai: no overflow in those cases. Might look bad. Inclination when making demos is not requiring unsafe keyword felt more natural.<br> <keithamus> iank_: that would mean you couldnt... how would you get it to start from bottom and scroll up? Unsafe end?<br> <keithamus> fantasai: safe end content would overflow toward bottom, scroll to top. unsafe end content overlflows to top and you scroll to bottom. If you dont specify safe/unsafe what happens?<br> <keithamus> fantasai: we can be consistent with flex/grid, or block which is safe-end<br> <kizu> q+<br> <keithamus> fantasai: want to avoid stuff in an unreachable region. On scroll container itself you dont have that problem<br> <keithamus> iank_: weak preference align-content: end starts at bottom and scrolls upward. For consistency with flexbox. Folks know flexbox works that way. Might not be webcompat<br> <rachelandrew> +1<br> <astearns> ack kizu<br> <keithamus> kizu: ideally Id like to see safe... author intent wont always mean we want to see bottom of scroll container<br> <keithamus> kizu: for block level we might want to think about if we want safe in css in general. Might be a good idea. Container which could have title, paragraph, if not enough content user will see header always, if unsafe as we add paragraphs it'll shift in which we wont see header.<br> <keithamus> kizu: safe is better than to assign position offset.<br> <keithamus> kizu: recently I think there was an article about align-content end in flex aligns to bottom, changing scroll origin<br> <keithamus> kizu: this was news for a lot of authors. People don't expect this behavior. top of box is always at top. flex is IMO not the same but webcompat default. Safe way for doing for block I'm for it, not strongly.<br> <astearns> ack fantasai<br> <keithamus> fantasai: want to point out flex already works this way. there has been bugs in impls which means content got clipped. Not been usable behavior until recently.<br> <keithamus> fantasai: Id like to hear from authors in group. align content end starts scroll at bottom?<br> <keithamus> fantasai: not overflow in that direction<br> <keithamus> fantasai: consistency arguments in both directions. Scroll containers in flexbox and grid scroll to bottom with align-content: end<br> <keithamus> fantasai: block contains, which aren't scroll container, align-content: start<br> <keithamus> fantasai: from authoring it might make more sense to be complicit with grid/flex.<br> <keithamus> fantasai: safety aspect - its not unsafe to start scroll container at bottom<br> <keithamus> fantasai: recently introduced alignment safety for unreachable content. Not a problem here.<br> <keithamus> fantasai: if you want the other behavior you can get it by specifying safe<br> <keithamus> iank_: IME align-content: end in flexbox is super useful. One reason to explicitly use flexbox. I'd lean to cosnsistency there<br> <keithamus> astearns: kizu disagreeing? People mention the behavior is unexpected?<br> <keithamus> kizu: to clarify not unexpected in a bad way. A feature they didn't know they could use. I'm okay with fantasai's resolution.<br> <dbaron> I find it a little weird that "safe" undoes an alignment that isn't actually unsafe.<br> <keithamus> iank_: when I talk to developers they say its amazing<br> <keithamus> dbaron: if you explicitly write safe it undoes something which wasnt unsafe? Consistency in what safe means might be valuable<br> <keithamus> fantasai: I dont think we should change explicit keyword behavior<br> <keithamus> fantasai: we might want to allow explicit direction when not overflowing. dont have that feature yet<br> <keithamus> PROPOSED RESOLUTION: all scroll containers default to unsafe alignment (not actually unsafe on scroll container)<br> <keithamus> PROPOSED RESOLUTION: all scroll containers default to unsafe alignment (not actually unsafe on scroll container)<br> <keithamus> dholbert: its not unsafe if it runs off direction if scrolling is able to move but what if it runs off in both directions?<br> <keithamus> dholbert: or offset by 100px to start side or whatever<br> <keithamus> fantasai: that would be clipped anyway<br> <keithamus> fantasai: the spec requires scroll up and down. you have to scroll to a position to align the subject within the container in both start and end so you can see entire alignment<br> <lea> (just realized I never did)<br> <keithamus> fantasai: if you position outside of alignment object it'll be off<br> <keithamus> RESOLVED: all scroll containers default to unsafe alignment (not actually unsafe on scroll container)<br> <keithamus> fantasai: in draft. just wanted confirmation<br> <keithamus> fantasai: will upload wpts<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10008#issuecomment-2023295784 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 27 March 2024 16:51:28 UTC