Skip to content

[css-containment] reuse "ink overflow" terminology #396

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
frivoal opened this issue Aug 10, 2016 · 1 comment
Closed

[css-containment] reuse "ink overflow" terminology #396

frivoal opened this issue Aug 10, 2016 · 1 comment

Comments

@frivoal
Copy link
Collaborator

frivoal commented Aug 10, 2016

This is a follow up form https://lists.w3.org/Archives/Public/www-style/2016Feb/0320.html which was left unresolved.

point 3 of item https://drafts.csswg.org/css-containment/#containment-layout says this:

If the contents of the element overflow the element, they must not project any "geometry" beyond the element’s normal bounds. In particular, any overflow must not be capable of causing the element’s ancestors to overflow; as far as the ancestors are concerned, the element is perfectly confined to its normal width×height bounds.

As far as I can tell, this is trying to define an effect identical to ink overflow, as defined in https://www.w3.org/TR/css-overflow-3/#ink.

Rather than redefining it, we should just reuse that term:

If the contents of the element overflow the element, they must be treated as ink overflow

@frivoal
Copy link
Collaborator Author

frivoal commented Sep 5, 2016

@tabatkins: If you're OK with this editorial change, I can go ahead and fix the spec, just give me the green light.

If you think the change would have non editorial consequences, I'd like to hear what these would be, because I don't think there should be any.

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

No branches or pull requests

2 participants