on for details.

## More than one lock
When stacked more is active (default) only one (last) component would be active.

## Over isolation
That could happen - 
you disable scroll on the body, 
you are suppressing all scroll and wheel events,
and you are ghosting the rest of the page by the `inert` prop.

Only something inside Lock does exists for the browser, and that might be less than you expected.

Dont forget about `shard`, dont forget - `inert` is not portals friendly, dont forget - you dont need over isolation in most of the cases.

> just be careful! 

# Performance
To do the job this library setup _non_ passive event listener. Chrome dev tools would complain about it, as a 
performance no-op.

We have to use synchronous scroll/touch handler, and it may affect scrolling performance.

Consider using `noIsolation` mode, if you have large scrollable areas.

# Supported React versions
- v1 supports React 15/16
- v2 requires 16.8.0+ (hooks)

# Scroll-Locky
This is a refactoring of another library - [react-scroll-locky](https://github.com/theKashey/react-scroll-locky) -
to make package smaller and more react-portals friendly.

## See also
 - [react-focus-on](https://github.com/theKashey/react-focus-on) - Finite Modal creator (uses Scroll-Locky) underneath.
 - [react-locky](https://github.com/theKashey/react-locky) - React event canceler
 - [react-scrolllock](https://github.com/jossmac/react-scrolllock) - React scroll lock
 - [scroll-lock](https://github.com/FL3NKEY/scroll-lock) - DOM scroll lock
 - [body-scroll-lock](https://github.com/willmcpo/body-scroll-lock) - DOM scroll lock
 
 > This package is relative smaller(1), more react friendly(2), works with non zero body margins(3), and has a better "overscroll" management. 

# License
MIT