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

fix: prevent issue with double-scrollbars in really specific circumstances #1370

Merged
merged 2 commits into from
Nov 18, 2024

Conversation

laurelfulford
Copy link
Contributor

All Submissions:

Changes proposed in this Pull Request:

This came out of our RAS-ACC beta testing: if you have a really specific setup for campaigns, you can get a double-scrollbar in an overlay. It's totally an edge case, but this will hopefully prevent it going forward!

How to test the changes in this Pull Request:

  1. If on a Mac, enable your scrollbars all the time under System Settings -- this just makes it easier to test.
  2. Make an overlay campaign and add contents pretty long and will require scrolling.
  3. On the front end, make the browser window shorter than the campaign will be, then load a page that the campaign will show on. Note the double scrollbar:

CleanShot 2024-11-18 at 12 05 48

  1. Apply this PR and run npm run build.
  2. Confirm that you only have one scrollbar now:

CleanShot 2024-11-18 at 12 06 58

  1. Do a bit of smoke testing to make sure your longer popups still scroll (just with one bar) with different settings, just in case!

Other information:

  • Have you added an explanation of what your changes do and why you'd like us to include them?
  • Have you written new tests for your changes, as applicable?
  • Have you successfully ran tests with your changes locally?

@laurelfulford laurelfulford merged commit c35772f into trunk Nov 18, 2024
8 checks passed
@laurelfulford laurelfulford deleted the fix/double-scrollbar branch November 18, 2024 20:43
Copy link

Hey @, good job getting this PR merged! 🎉

Now, the needs-changelog label has been added to it.

Please check if this PR needs to be included in the "Upcoming Changes" and "Release Notes" doc. If it doesn't, simply remove the label.

If it does, please add an entry to our shared document, with screenshots and testing instructions if applicable, then remove the label.

Thank you! ❤️

@laurelfulford
Copy link
Contributor Author

Thanks @chickenn00dle! 🥳

matticbot pushed a commit that referenced this pull request Nov 29, 2024
## [3.1.5-alpha.1](v3.1.4...v3.1.5-alpha.1) (2024-11-29)

### Bug Fixes

* hide cpt from menu ([#1365](#1365)) ([6ec34ee](6ec34ee))
* prevent issue with double-scrollbars in really specific circumstances ([#1370](#1370)) ([c35772f](c35772f))
@matticbot
Copy link
Contributor

🎉 This PR is included in version 3.1.5-alpha.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

matticbot pushed a commit that referenced this pull request Dec 9, 2024
## [3.1.5](v3.1.4...v3.1.5) (2024-12-09)

### Bug Fixes

* hide cpt from menu ([#1365](#1365)) ([6ec34ee](6ec34ee))
* prevent issue with double-scrollbars in really specific circumstances ([#1370](#1370)) ([c35772f](c35772f))
@matticbot
Copy link
Contributor

🎉 This PR is included in version 3.1.5 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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.

3 participants