- From: Ian Kilpatrick via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Oct 2023 22:30:44 +0000
- To: public-css-archive@w3.org
> 15. If you're capping by max-height, and the cut-off point falls into something that has more structure than just a pile of lines (nestbed BFCs, block-level orthogonal flow, a table, a grid, a block level image…), what do you do? If the content isn't on a line it will cut off the content outside the formatting context - this is similar to monolithic content. As with 14 they aren't considered for lines. > 16. What do you get if you use any of the JS APIs to query about the geometry of boxes entirely within the discarded/collapsed content? You get the standard geometry as you'd expect if they weren't hidden. This is similar to how `visibility: hidden` works. > 17. What do you get if you use any of the JS APIs to query about the geometry of boxes partially within the discarded/collapsed content? Same as above. They will be visible if not hidden, and same the same geometry. > 18. How do the intrisinsic size keywords resolve on the height of the truncating/containing box? Unclear what you mean by truncating here, but I'll assume this is the box with line-clamp on it. It'll be the height of it in the clamped state. > 19. How do the intrisinsic size keywords resolve on the truncated box? Unclear what tracated box means here, but i'll assume a box that was been hidden. It'll behave the same as if it wasn't truncated. > 20. How do you insert the ellipsis text on the last line that remains: These questions don't seem specific to the "collapse" behaviour. > 21. What happens when you select all on the page and copy to the clipboard? Do we get the hidden content? What about the ellipsis? Unclear - what the expected behaviour would be - this is similar to existing clamping behaviour (e.g. text-overflow). > 22. Is the discarded content in the accessibility tree? Likely yes. -- GitHub Notification of comment by bfgeek Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7708#issuecomment-1747736859 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 4 October 2023 22:30:46 UTC