Forum Discussion
Dev channel update to 95.0.997.1 is live
Hello Insiders! Today we’re releasing build 95.0.997.1 to the Dev channel. That’s right, it’s already time for 95! Because of that, look for version 94 to be coming to Beta soon. We’ve also got a...
This update breaks JavaScript import path resolution under certain circumstances. When reloading certain pages, which are using relative import paths for JS-Modules and while having DevTools enabled, the import gets resolved as an absolute import, not relative to the current page, resulting in 404 errors.
This does not happen, when "Disable Cache" is active in the DevTools and I cannot reproduce it in a private Window. But I can reproduce it without any enabled extensions reliably after 2-3 reloads on some pages. For example: https://portal.sozialbank.de/girocard-bestellformular/
- This Javscript issue appears to be a transient error we inherited from Chromium. I can still reproduce it in their Dev build, but not their Canary build. And since their Canary is usually a couple of days ahead of ours, I expect this to be fixed in our Canary build in a couple of days.
- Thank you for the quick reply and finding the source of this bug.
- I've checked it in my Debian 11 rig and the page went blank after 2-3 reloads. Ctrl-F5 helped.
- Intresting, I wonder if this is what is breaking it on very specific desktop-environments. I am running it on Budgie perfectly fine.
- I can reproduce the Javascript issue on Windows too, so it looks to be a different issue.
