Kyle Tsang

I don't see this issue with these deps on one of my projects: ``` "react": "^18.2.0", "react-bootstrap": "^2.4.0", "react-dom": "^18.2.0", "typescript": "^4.6.3" "@types/react": "^18.0.14", "@types/react-dom": "^18.0.5", ```

@jquense could this be caused by missing initial styles in `usePopper`? I noticed this was in `react-overlays` and not `@restart/ui`. ``` const initialPopperStyles = ( position: string, ): Partial =>...

Just tested with the above and it looks like it fixes the issue

Haven't seen this myself on Windows or an intel mac. What version of nodejs are you using? Can you upgrade Chrome to the latest?

Could you try downgrading to node 14 and see if that works?

With the ability to set `min` and `max` on a range, you shouldn't be running into any validation issues because all of your values should be valid? Could you go...

In general, none of the utility classes are prefixed, only the components are. Have you looked at this? https://getbootstrap.com/docs/5.1/customize/sass/

Looks like the props are spread into the dialog element, so we could potentially narrow the types to use `HTMLAttributes`. Not sure if there were other reasons for using this...

That's intended. The ref gives you the instance of the modal manager used in `@restart/ui` https://github.com/react-restart/ui/blob/4551ef5cb3465bbe19381bd3d14db3aa30a00f5f/src/Modal.tsx#L258

A workaround could be to disable GPU acceleration in popper. I tested this on Windows 10 Chrome 83.0.4103.97 and the horizontal scroll no longer appears. ``` const config = {...