Skip to content

Fix loading indicator still displayed after opening out-of-scope URLs#712

Merged
filips123 merged 1 commit intofilips123:mainfrom
Joshix-1:main
Jul 26, 2025
Merged

Fix loading indicator still displayed after opening out-of-scope URLs#712
filips123 merged 1 commit intofilips123:mainfrom
Joshix-1:main

Conversation

@Joshix-1
Copy link
Copy Markdown
Contributor

still restarts websockets, which is not ideal, but it makes firefox pwas usable

I have no idea how anything works, or why it does what it does, but I saw someone on stackoverflow using Cr.NS_BINDING_ABORTED and tested that and it works for me

https://stackoverflow.com/questions/30585385/firefox-extension-how-to-intercept-the-requested-url-conditionally-and-block-it

not a teapot
@filips123
Copy link
Copy Markdown
Owner

Thanks for the fix! That is quite interesting, and I also don't know why this happens. I wanted to have 418 as an easter egg, but I guess it will have to be removed.

I also found that https://echo.websocket.org/.ws is quite a useful site for testing WebSockets. I think the problem is that as the link was supposed to be opened in the same tab as the original website, Firefox cancelled all ongoing requests before PWAsForFirefox could prevent the navigation. But I don't know yet how to prevent this. Maybe there is some event other than http-on-modify-request that executes earlier.

@filips123 filips123 merged commit 33642ae into filips123:main Jul 26, 2025
17 checks passed
@filips123 filips123 moved this to Done in PWAsForFirefox Jul 26, 2025
@filips123 filips123 changed the title fix #381 Fix loading indicator still displayed after opening out-of-scope URLs Jul 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants