-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Chrome has overflow issues with some position-area
values
#27573
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
Conversation
@bfgeek @tabatkins given that this bug impacts most usage of this feature, it seems reasonable to mark it as |
position-area
values
@ddbeck Do you have any concerns with marking those Alternatives considered were marking |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not an expert in this feature, but this seems like a reasonable partial to me. I didn't count these up—do they apply to every single-value use of the property or some but not all values as single values? If it's only specific values, then I like that it's specifically targeted to the affected values and not the property in general.
I have a couple of suggestions for the notes—which I hope you'll consider despite the implied hassle of applying them to all of the notes—but I'll mark approved anyway.
Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs). |
Yeah, it's only specific single values. Although e.g |
I'm happy for this to land when others are. |
position-area
valuesposition-area
values
Summary
position-area
in Chrome has a fundamental bug where the content of the element overflows the viewport, obscuring content. It's important to work around this.Test results and supporting details
https://issues.chromium.org/issues/438334710