Matthew Holloway

@dviry fyi I solved this by importing all CSS from a single file, and for code-split styles I'll migrate to a CSS-in-JS approach (probably ~~[Glamor](https://github.com/threepointone/glamor)~~ **`styled-components`**).

Applied a general fix in #6066b7dd53917ba88aa3ce5aee873263e4676a46 Will fix properly later.

Nice one @fallais !

Any update on this?

@CalinDale I believe this was done to avoid undoing native styling, however this decision was done before my time on RAA

@CalinDale to use native elements we would affect the styling (the CSS needed) in order to undo native styles, but that's all quite doable and I'm happy to go ahead...

First step might be to describe the current markup, and your recommended markup.

There's no scroll management in React-Accessible-Accordion, so any scrolling will be based on the user moving focus to an element which the browser then scrolls to. Do you have a...

Found this thread in 2019... just fyi Google Puppeteer is how you do this now https://github.com/GoogleChrome/puppeteer/blob/v1.12.2/docs/api.md#pagepdfoptions

Is there a plan to release this?