On longstanding webcompat issue about padding-bottom/padding-right missing in scroll containers
92 views
Skip to first unread message
Ting-Yu Lin 林庭宇
unread,
Mar 25, 2021, 3:20:57 PM3/25/21
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to dev-platform
Over the years, we accumulate a lot of duplicates in Bug 748518
<https://bugzilla.mozilla.org/show_bug.cgi?id=748518> about
`overflow:auto/scroll` container's padding-bottom / padding-right is
missing in Firefox when scrolling to the bottom / right. Blink and WebKit
have this behavior for most container types [1], and web developers are
expecting this rendering.
Blink and WebKit's behavior is not consistent. Currently, both engines only
add inline-end padding to the inline children but not to the block
children. Wait for a resolution on spec issue #129
<https://github.com/w3c/csswg-drafts/issues/129>.
Bug 1527539 <https://bugzilla.mozilla.org/show_bug.cgi?id=1527539>: add
grid container's padding and grid item's margin in both axes for scroll
grid container.
No plan yet, but I hope I can get to it in Firefox 89 or 90.
Could you please summarize what the table ends up looking like after
these changes? I also saw bz note that we only want to change our
behavior once in this area, but I guess since this has taken so long
to resolve we changed our mind on that and will now proceed in two
stages?
Ting-Yu Lin 林庭宇
unread,
Mar 26, 2021, 6:00:29 PM3/26/21
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Anne van Kesteren, dev-platform
> Could you please summarize what the table ends up looking like after
these changes?
> I also saw bz note that we only want to change our behavior once in this
area, but I guess since this has taken so long to resolve we changed our
mind on that and will now proceed in two stages?
Right, it's best we don't change our behavior back and forth. With Bug
1527949 <https://bugzilla.mozilla.org/show_bug.cgi?id=1527949> fixed
(already in Nightly), I believe it resolved most of the webcompat issues on
this subject, and we can deal with other bugs that have less webcompat
demanding later.