W3C home > Mailing lists > Public > public-css-archive@w3.org > September 2020

Re: [csswg-drafts] [css-break-4] Should fragmentation of block-level replaced-elements be configurable? ("object-slice") (#3404)

From: Mike Bremford via GitHub <sysbot+gh@w3.org>
Date: Tue, 29 Sep 2020 12:41:12 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-700675579-1601383270-sysbot+gh@w3.org>
We like the proposal to use `break-inside`. I was going to argue for keeping the two values `auto` and `avoid`, with no new value `allow`, and adding something like this in the user-agent stylesheet rules for HTML:
img, svg, math, embed, canvas, object { break-inside: avoid }
Easy enough, except `object` is not always replaced - it depends on whether the "fallback content" is rendered.

So I figure you either 1) need to some way to determine whether the fallback content is rendered in object, maybe `object:empty` or `object:valid`, 2) add something like a `:replaced` selector, or 3) add `break-inside: allow` and have `auto` collapse to `avoid` or `allow` based on replacedness, as suggested by @fantasai. I recall that selectors reflecting the load state of the DOM aren't too popular around here, so that leans towards 3.

GitHub Notification of comment by faceless2
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3404#issuecomment-700675579 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 29 September 2020 12:41:13 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:17 UTC