-
Notifications
You must be signed in to change notification settings - Fork 719
[css-overflow-3] Scrollable Overflow contributions of zero height/width elements #4791
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
Comments
We seem to have interop across Gecko/Blink/WebKit that the tall block-level element contributes to overflow, and none of the others do. |
Specifically for the inflow case this is affecting the "inflow" bounds, the element isn't directly contributing overflow itself. You can test this by adding a transform to both elements - neither affect the scrollable area. |
The CSS Working Group just discussed The full IRC log of that discussion |
OK, 1. so the testcases need to add html, body { height: 0; } to work properly and 2. we need to spec that boxes with empty area do not contribute to scrollable overflow. If I understood @bfgeek correctly? |
Thats correct. At least "directly" to scrollable overflow. They can indirectly contribute to scrollable overflow via something like: >
<div style="width: 100px; height: 100px; overflow: scroll; display: grid;">
<div style="width: 0; height: 120px; outline: solid red;">div>
<div style="width: 120px; height: 0; outline: solid green;">div>
div> |
The CSS Working Group just discussed
The full IRC log of that discussion |
@bfgeek Edited into https://drafts.csswg.org/css-overflow-3/#scrollable |
@fantasai Is there anything left with this issue? |
@MrHBS No, just wanted to ask @bfgeek to sign off that the edits are correct. |
It appears that, at least in some implementations, zero-width elements do not contribute to the horizontal overflow, but zero-height elements do contribute to the vertical overflow.
So overall it seems that zero-sized things contribute in the block axis but not the inline axis.
This is kinda weird, but if it's required for Web-compat we should spec it.
The text was updated successfully, but these errors were encountered: