The api-docs is extremely laggy and unresponsive. Not sure what the deal is, seems like misbehaving JavaScript. But we can’t use it.
Win11 Pro, issue with MS Edge and Chrome
It is a very large openapi file, so it may take a while to fully render and be usable.
I understand that, but I don’t think that’s the issue. For example, it constantly scrolls back to top and even when the page is fully loaded clicking on the first API will work but then clicking on another will not. There’s something else going on. If you look at the browser task manager the CPU usage is constantly high and the memory usage is very high.
Is it the same across all browsers for you?
I’m not able to replicate on chrome.
Try searching for ‘documents’ and then clicking the ‘Documents’ group option.
Tested on the following with the same behavior.
Win11 Desktop and Win11 Laptop, Edge, Chrome & Firefox dev edition
Tested on my Mac Air M3 Edge has the same issue, Safari takes time on first load but is more responsive than anything else. However, when scrolling through the API’s the menu blanks out for a bit and takes a while to render
On the laptops the memory usage creeps up slower than my desktop but I assume that’s probably because I have a lot of ram on the desktop.
Looking at the performance metrics, it looks like it’s spending a lot of time recalculating styles, even when nothing is happening on the site.
Spent a bit more time to make sure there wasn’t a plugin or something else across my pc’s that might be the issue. Installed Chrome on the mac and saw the same thing. I think the M3 chip just works the problem faster than pc’s.
Looked into the standalone.js and realized its part of @scalar/api-reference. You’re on 1.28.14 which looks like it’s the latest release. Probably needs to escalate to their discord or GitHub issues for their take.
