Skip to content
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

Decouple Modal's scrollbar functionality #33245

Merged
merged 2 commits into from
Apr 11, 2021

Conversation

GeoSot
Copy link
Member

@GeoSot GeoSot commented Mar 2, 2021

Scorllbar. js is the exact same code of modal.js which handles all the scrollbar functionality.
It is extracted, self-tested and used on Offcanvas with success, and it can be used on modal.js through methods

preview

@GeoSot GeoSot requested review from a team as code owners March 2, 2021 22:49
@GeoSot
Copy link
Member Author

GeoSot commented Mar 2, 2021

Please can somebody explain me the usage and the checks of this code block?

    if ((!isBodyOverflowing && isModalOverflowing && !isRTL()) || (isBodyOverflowing && !isModalOverflowing && isRTL())) {
      this._element.style.paddingLeft = `${scrollbarWidth}px`
    }

    if ((isBodyOverflowing && !isModalOverflowing && !isRTL()) || (!isBodyOverflowing && isModalOverflowing && isRTL())) {
      this._element.style.paddingRight = `${scrollbarWidth}px`
    }

@alpadev
Copy link
Contributor

alpadev commented Apr 7, 2021

Please can somebody explain me the usage and the checks of this code block?

    if ((!isBodyOverflowing && isModalOverflowing && !isRTL()) || (isBodyOverflowing && !isModalOverflowing && isRTL())) {
      this._element.style.paddingLeft = `${scrollbarWidth}px`
    }

    if ((isBodyOverflowing && !isModalOverflowing && !isRTL()) || (!isBodyOverflowing && isModalOverflowing && isRTL())) {
      this._element.style.paddingRight = `${scrollbarWidth}px`
    }

I can be wrong about this but I think this got something to do with issues about modal shifting/jumping or not being centered with/without scrollbars on the body.

Found it: #14933

But that's not everything.. I decided to go down the rabbit hole.

So let's begin:

isBodyOverflowing is using getBoundingClientRect() to check if the body's width is less than the window's innerWidth ("the viewport width including the size of a rendered scroll bar (if any)"). My guess, this was done to see if there is a scrollbar on the document root or not. (I was a bit confused as we compare widths but yeah - the overflow means on the y-axis.)

isModalOverflowing is checking if the element's scrollHeight ("the height of an element's content, including content not visible on the screen due to overflow.") is bigger than the document root's clientHeight ("the viewport height excluding the size of a rendered scroll bar (if any)."). My guess, this was done to see if the modal is higher than the document root and would cause a scrollbar.

The paddingLeft is set to shift the modal dialog to the right and create a spacing (the size of a scrollbar) and vice versa. My guess, this was done to compensate for a scrollbar on the opposite side.

Thoughts:

So I checked the examples in our documentation and this doesn't seem to work properly. (This is true for older Bootstrap versions too. Maybe it did at some point tho.) The result, the dialog isn't centered properly. (At least in FF and Chrome on Windows. Safari 14 and Chrome on Android is fine tho.)
This is partly caused by the fact that when we meassure scrollHeight the dialog isn't yet visible so it's 0 and isModalOverflowing is always false.

About isRTL(). If I add dir="rtl" to the html tag the body's scrollbar is still on the right side. The modal's scrollbar on the left. 🤯 Not sure how that is handled when the OS is set rtl.

In general without those extra paddings it seems to work fine for me.

@GeoSot
Copy link
Member Author

GeoSot commented Apr 7, 2021

@alpadev what a lovely approach 🛩️

129 line this._adjustDialog() is pointless for sure, cause it hidden as you told

I am not sure for the other two usages (resize 304 / handleUpdate 211)
Did you test it on resize too?

And one more cherry, that is out of this scope: lines 405|407 & 414|419 seems redundant as element overflow-y is auto

@alpadev
Copy link
Contributor

alpadev commented Apr 7, 2021

I am not sure for the other two usages (resize 304 / handleUpdate 211)
Did you test it on resize too?

So I made a codepen for the case when the body doesn't overflow. Since isModalOverflowing is false there is no padding added so it looks good. If I resize isModalOverflowing becomes true and it's adding padding-left that makes it not centered. (Case !isBodyOverflowing && isModalOverflowing && !isRTL())

I tried it on the documentation page. There is padding-right added because the body does overflow (Case isBodyOverflowing && !isModalOverflowing && !isRTL()).

There is no case for when both are overflowing or both are not overflowing.

Also the _adjustDialog is only adding paddings but never take them away. So at some point it's adding paddings making it uncentered and they will never go away until closed.

@alpadev
Copy link
Contributor

alpadev commented Apr 7, 2021

And one more cherry, that is out of this scope: lines 405|407 & 414|419 seems redundant as element overflow-y is auto

My guess this was added so in case when you click on a static backdrop and it would do this little animation, it's not causing any scrollbars on the backdrop if it reaches outside but not sure.

@alpadev
Copy link
Contributor

alpadev commented Apr 7, 2021

Likely related: #31845

@GeoSot GeoSot force-pushed the use-scollbarjs-on-modal branch 2 times, most recently from ee866fe to 8538f88 Compare April 7, 2021 09:35
@GeoSot
Copy link
Member Author

GeoSot commented Apr 7, 2021

@alpadev REALLY HELPFUL
I will not touch it on this pr but nice to have it in mind too
Issue created #33580

Any other comments over the changes?

Copy link
Contributor

@alpadev alpadev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything else LGTM 👍

@@ -8,7 +8,7 @@
import SelectorEngine from '../dom/selector-engine'
import Manipulator from '../dom/manipulator'

const SELECTOR_FIXED_CONTENT = '.fixed-top, .fixed-bottom, .is-fixed'
const SELECTOR_FIXED_CONTENT = '.fixed-top, .fixed-bottom, .is-fixed, .sticky-top'

This comment was marked as resolved.

Copy link
Member Author

@GeoSot GeoSot Apr 8, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wish would be me :P

In this PR I just remove the copied the code, out of modal.
It was written like this. I am trying to finish this and a new issue waits #33580 (afraid of how many tests need to tweak)

This comment was marked as resolved.

@rohit2sharma95
Copy link
Collaborator

My guess this was added so in case when you click on a static backdrop and it would do this little animation

That animation is transform scale, and transforming any element does not affect the layout of the real DOM element 🤔

@@ -49,7 +49,7 @@ const reset = () => {
const _resetElementAttributes = (selector, styleProp) => {
SelectorEngine.find(selector).forEach(element => {
const value = Manipulator.getDataAttribute(element, styleProp)
if (typeof value === 'undefined' && element === document.body) {
if (typeof value === 'undefined') {
Copy link
Collaborator

@rohit2sharma95 rohit2sharma95 Apr 9, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was just thinking if the value was not stored on the data attribute then why the style prop it is being removed from the element? 🤔

Since if the value here:

const value = Manipulator.getDataAttribute(element, styleProp)

is undefined, it means that the style prop was not added by the bootstrap and that's why should not be removed (that style prop might be present on the dom element already added by the end-user)

Copy link
Member Author

@GeoSot GeoSot Apr 9, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you are right on this.
I will keep it as default, and we can discuss it on a next PR

@alpadev
Copy link
Contributor

alpadev commented Apr 9, 2021

My guess this was added so in case when you click on a static backdrop and it would do this little animation

That animation is transform scale, and transforming any element does not affect the layout of the real DOM element 🤔

@rohit2sharma95 Check for yourself 🙂 https://jsfiddle.net/z1pb7c9w/

@XhmikosR XhmikosR changed the title Decouple scrollbar functionality on Modal.js using Scrollbar.js Decouple Modal's scrollbar functionality Apr 11, 2021
@XhmikosR XhmikosR merged commit 7b7f4a5 into twbs:main Apr 11, 2021
@XhmikosR
Copy link
Member

XhmikosR commented Apr 11, 2021

@GeoSot BrowserStack tests broke. Please temporarily push any PRs that are not made from an upstream branch so that you check if everything is fine before we merge :)

EDIT: NVM, it seems it was just a fluke. That being said, let's make sure BrowserStack tests pass for PRs coming from your fork.

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

Successfully merging this pull request may close these issues.

4 participants