Hello and thank you for the additional info max, I think I reproduced the issue on the latest Release (109.0.1/20230127170202) and Beta () under Ubuntu 16.04 LTS. I got some trouble with launching Nightly on Linux for some reason and could not test there but will try again soon. I did the following on Release: 1. Loaded the extension you provided via about:debugging 2. Without accessing Settings as I presume the handler is set to “Use test-protocol debug dialog (default)”, I access Wikipedia and invoke the add-on action → nothing happens, no doorhanger or errors/messages in consoles 2. Accessed Settings and changed handler to “Always ask”, switched to the tab with Wikipedia and invoked the add-on action → nothing happens again 3. Closed Settings, opened Settings again and noticed the handler was reset to default I did not see any “choose application to open the … link” doorhanger at all on Release and I tried with 2 different profiles. On Beta: 1. Loaded the extension you provided via about:debugging 2. Without accessing Settings as I presume the handler is set to “Use test-protocol debug dialog (default)”, I access Wikipedia and invoke the add-on action → I get the “Allow the extension Scheme handler – location to open the test protocol link with test-protocol debug dialog?” doorhanger 3. I choose to “Open Link” 4. Accessed Settings and changed handler to “Always ask” 5. Switched to the tab with Wikipedia and invoked the add-on action → got the “choose application” doorhanger 6. Closed Settings, opened Settings again and the handler was not reset to default 7. Switched to the tab with Wikipedia and invoked the add-on action → got the “choose application” doorhanger and clicked “Choose Application” (nothing happened) 8. Refreshed Settings and the handler was reset to default but I do still get the “choose application” doorhanger on Wikipedia when I invoke the add-on. At this point I’m not sure if I reproduced the issue or not, but the handler does get reset, although it appears to vary on how it happens.
Bug 1813975 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Hello and thank you for the additional info max, I think I reproduced the issue on the latest Release (109.0.1/20230127170202) and Beta (110.0b9/20230202190127) under Ubuntu 16.04 LTS. I got some trouble with launching Nightly on Linux for some reason and could not test there but will try again soon. I did the following on Release: 1. Loaded the extension you provided via about:debugging 2. Without accessing Settings as I presume the handler is set to “Use test-protocol debug dialog (default)”, I access Wikipedia and invoke the add-on action → nothing happens, no doorhanger or errors/messages in consoles 2. Accessed Settings and changed handler to “Always ask”, switched to the tab with Wikipedia and invoked the add-on action → nothing happens again 3. Closed Settings, opened Settings again and noticed the handler was reset to default I did not see any “choose application to open the … link” doorhanger at all on Release and I tried with 2 different profiles. On Beta: 1. Loaded the extension you provided via about:debugging 2. Without accessing Settings as I presume the handler is set to “Use test-protocol debug dialog (default)”, I access Wikipedia and invoke the add-on action → I get the “Allow the extension Scheme handler – location to open the test protocol link with test-protocol debug dialog?” doorhanger 3. I choose to “Open Link” 4. Accessed Settings and changed handler to “Always ask” 5. Switched to the tab with Wikipedia and invoked the add-on action → got the “choose application” doorhanger 6. Closed Settings, opened Settings again and the handler was not reset to default 7. Switched to the tab with Wikipedia and invoked the add-on action → got the “choose application” doorhanger and clicked “Choose Application” (nothing happened) 8. Refreshed Settings and the handler was reset to default but I do still get the “choose application” doorhanger on Wikipedia when I invoke the add-on. At this point I’m not sure if I reproduced the issue or not, but the handler does get reset, although it appears to vary on how it happens.