Prevent page scrolling when the modal box is opened
Have you ever encountered this situation: Open a modal box, scroll in it, close it, and the page jumps to another location?
This is because the modal box is just an element on the page, it may remain in place, but the rest of the page is still functioning properly.
Sometimes this doesn't matter, such as when the screen height is exactly equal to the viewport height. But in other cases, a scrolling problem occurs. The good news is that we can prevent this with some CSS (and JavaScript) tricks.
Start with a simple solution
We can significantly reduce the problem of page scrolling when the modal box is opened by setting the height of the entire body to the full viewport height and hiding vertical overflow when the modal box is opened:
<code>body.modal-open { height: 100vh; overflow-y: hidden; }</code>
This is good, but if we have scrolled through the page elements before opening the modal box, there will be a slight horizontal rearrangement. The viewport width increases by about 15 pixels, which is exactly the width of the scrollbar. Let's adjust the right fill of the body a little to avoid this.
<code>body { height: 100vh; overflow-y: hidden; padding-right: 15px; /* 避免寬度重排*/ }</code>
Note that the height of the modal box must be less than the viewport height for this method to work. Otherwise, the scroll bar on the body will be necessary.
What to do on mobile?
This solution works well on both desktop and Android mobile. However, iOS Safari needs more processing because the body still scrolls when the modal box opens when clicking and moving on the touch screen.
We can set the body to fixed positioning as a solution:
<code>body { position: fixed; }</code>
It's OK now! When touching the screen, the body will not respond. However, there is still a "small" problem here. Assuming the modal box trigger is at the bottom of the page, we click to open it. very good! But now we automatically scroll to the top of the screen, which is as confusing as the scrolling behavior we are trying to solve.
Oops!
So we need to use JavaScript
We can use JavaScript to avoid the bubble of touch events. We all know that there should be a background layer when the modal box is opened. Unfortunately, in iOS, stopPropagation is a bit awkward to work with touch events. But preventDefault works very well. This means we have to add event listeners to each DOM node included in the modal box—not just on the background or modal box layer. The good news is that many JavaScript libraries can do this, including the proven jQuery.
One more thing: What if we need to scroll inside the modal box? We still need to trigger the response to the touch event, but we still need to stop the bubbling when it reaches the top or bottom of the modal box. This seems very complicated, so we haven't completely solved the problem.
Enhanced fixed body method
What we are using is:
<code>body { position: fixed; }</code>
If we know the top position of scrolling and add it to our CSS, the body doesn't scroll back to the top of the screen, so the problem is solved. We can use JavaScript to calculate the scroll top and add that value to the body style:
// When the modal box is displayed, we need a fixed body document.body.style.position = 'fixed'; document.body.style.top = `-${window.scrollY}px`; // When the modal box is hidden, we need to keep it at the top of the scroll position document.body.style.position = ''; document.body.style.top = '';
This works, but there is still a little leak after the modal box is closed. Specifically, when the modal box is open and the body is set to fixed, the page seems to have lost its scrolling position. So we have to retrieve the location. Let's modify our JavaScript to solve this problem.
// When the modal box is hidden... const scrollY = document.body.style.top; document.body.style.position = ''; document.body.style.top = ''; window.scrollTo(0, parseInt(scrollY || '0') * -1);
nailed it! The body no longer scrolls when the modal box is open and remains in the scroll position when the modal box is open and closed. Long live!
The above is the detailed content of Prevent Page Scrolling When a Modal is Open. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

There are three ways to create a CSS loading rotator: 1. Use the basic rotator of borders to achieve simple animation through HTML and CSS; 2. Use a custom rotator of multiple points to achieve the jump effect through different delay times; 3. Add a rotator in the button and switch classes through JavaScript to display the loading status. Each approach emphasizes the importance of design details such as color, size, accessibility and performance optimization to enhance the user experience.

To deal with CSS browser compatibility and prefix issues, you need to understand the differences in browser support and use vendor prefixes reasonably. 1. Understand common problems such as Flexbox and Grid support, position:sticky invalid, and animation performance is different; 2. Check CanIuse confirmation feature support status; 3. Correctly use -webkit-, -moz-, -ms-, -o- and other manufacturer prefixes; 4. It is recommended to use Autoprefixer to automatically add prefixes; 5. Install PostCSS and configure browserslist to specify the target browser; 6. Automatically handle compatibility during construction; 7. Modernizr detection features can be used for old projects; 8. No need to pursue consistency of all browsers,

Themaindifferencesbetweendisplay:inline,block,andinline-blockinHTML/CSSarelayoutbehavior,spaceusage,andstylingcontrol.1.Inlineelementsflowwithtext,don’tstartonnewlines,ignorewidth/height,andonlyapplyhorizontalpadding/margins—idealforinlinetextstyling

Use the clip-path attribute of CSS to crop elements into custom shapes, such as triangles, circular notches, polygons, etc., without relying on pictures or SVGs. Its advantages include: 1. Supports a variety of basic shapes such as circle, ellipse, polygon, etc.; 2. Responsive adjustment and adaptable to mobile terminals; 3. Easy to animation, and can be combined with hover or JavaScript to achieve dynamic effects; 4. It does not affect the layout flow, and only crops the display area. Common usages are such as circular clip-path:circle (50pxatcenter) and triangle clip-path:polygon (50%0%, 100 0%, 0 0%). Notice

Setting the style of links you have visited can improve the user experience, especially in content-intensive websites to help users navigate better. 1. Use CSS's: visited pseudo-class to define the style of the visited link, such as color changes; 2. Note that the browser only allows modification of some attributes due to privacy restrictions; 3. The color selection should be coordinated with the overall style to avoid abruptness; 4. The mobile terminal may not display this effect, and it is recommended to combine it with other visual prompts such as icon auxiliary logos.

To create responsive images using CSS, it can be mainly achieved through the following methods: 1. Use max-width:100% and height:auto to allow the image to adapt to the container width while maintaining the proportion; 2. Use HTML's srcset and sizes attributes to intelligently load the image sources adapted to different screens; 3. Use object-fit and object-position to control image cropping and focus display. Together, these methods ensure that the images are presented clearly and beautifully on different devices.

The choice of CSS units depends on design requirements and responsive requirements. 1.px is used for fixed size, suitable for precise control but lack of elasticity; 2.em is a relative unit, which is easily caused by the influence of the parent element, while rem is more stable based on the root element and is suitable for global scaling; 3.vw/vh is based on the viewport size, suitable for responsive design, but attention should be paid to the performance under extreme screens; 4. When choosing, it should be determined based on whether responsive adjustments, element hierarchy relationships and viewport dependence. Reasonable use can improve layout flexibility and maintenance.

Different browsers have differences in CSS parsing, resulting in inconsistent display effects, mainly including the default style difference, box model calculation method, Flexbox and Grid layout support level, and inconsistent behavior of certain CSS attributes. 1. The default style processing is inconsistent. The solution is to use CSSReset or Normalize.css to unify the initial style; 2. The box model calculation method of the old version of IE is different. It is recommended to use box-sizing:border-box in a unified manner; 3. Flexbox and Grid perform differently in edge cases or in old versions. More tests and use Autoprefixer; 4. Some CSS attribute behaviors are inconsistent. CanIuse must be consulted and downgraded.
