Skip to content

Conversation

@szager-chromium
Copy link
Contributor

No description provided.

@chrishtr chrishtr requested a review from frivoal January 20, 2024 01:00
Copy link
Collaborator

@frivoal frivoal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems reasonable to me, and as far as I know, is the web-compatible behavior.

Co-authored-by: Chris Harrelson <3453258+chrishtr@users.noreply.github.com>
@css-meeting-bot
Copy link
Member

The CSS Working Group just discussed [css-overflow-3] Specify extent of ink overflow, and agreed to the following:

  • RESOLVED: Specify ink overflow extent for outline
The full IRC log of that discussion <Frances> GitHub-bot, take up #8649
<Rossen_> q?
<noamr> q+
<Frances> Florian: Ink-overflow or scroll-overflow, made a pr for ink-overflow. Need to discuss with the working group.
<chrishtr> +1 to ink overflow
<Frances> Florian: Wasn't defined until now
<Frances> fantasai: Correct that it needs to be ink overflow
<Rossen_> ack noamr
<Frances> Noam: Need to specify what ink overflow is
<Frances> fantasai: Doesn't cause the overflow area to expand
<fantasai> github: https://github.com//pull/9824
<fantasai> s/the overflow/scrollable/
<fantasai> noamr: but the extent isn't defined, that's what #8649 is about
<fantasai> [discussion about which issue to post to]
<fantasai> +1 to resolving on ink overflow
<dbaron> +1
<Frances> Rossen: Outlines are in ink overflow. Any objections?
<Frances> PROPOSAL: Specify ink overflow extent for outline
<Frances> RESOLVED: Specify ink overflow extent for outline
<fantasai> s/needs to be ink overflow/needs to be ink overflow, because scrollable overflow can trigger layout changes and point of outline is that it doesn't cause layout changes/
<fantasai> s/ink overflow extent for outline/outline as ink overflow/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants