Right now, css-overflow-3 section 2.2 says a scroll container's end-side padding is "optionally" scrollable: > The scrollable overflow region is the union of: [...] Optionally, additional padding on the end-edge sides, corresponding to the end-side padding of the scroll container" https://www.w3.org/TR/css-overflow-3/#scrollable We don't include this padding, but Chrome does. https://github.com/w3c/csswg-drafts/issues/129 is resolved on coming up with something more concrete for this, spec-wise. In the meantime, I'm filing this as a placeholder bug to implement this once we've got something to implement. Note that we do run into interop/webcompat issues due to this behavior difference, as documented in discussion/webcompat-see-also-links on https://bugzilla.mozilla.org/show_bug.cgi?id=748518 (which will hopefully become addressed when this is specced & implemented here).
Bug 1527949 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Right now, css-overflow-3 section 2.2 says a scroll container's end-side padding is "optionally" scrollable: > The scrollable overflow region is the union of: [...] Optionally, additional padding on the end-edge sides, corresponding to the end-side padding of the scroll container" https://www.w3.org/TR/css-overflow-3/#scrollable We don't include this padding, but Chrome does (though [only in the block axis](https://github.com/w3c/csswg-drafts/issues/129#issuecomment-221398848)). https://github.com/w3c/csswg-drafts/issues/129 is resolved on coming up with something more concrete for this, spec-wise. In the meantime, I'm filing this as a placeholder bug to implement this once we've got something to implement. Note that we do run into interop/webcompat issues due to this behavior difference, as documented in discussion/webcompat-see-also-links on https://bugzilla.mozilla.org/show_bug.cgi?id=748518 (which will hopefully become addressed when this is specced & implemented here).