1659609 - url does not work on first attempt

Status: RESOLVED WORKSFORME

(Core :: DOM: Service Workers, defect, P2)

Description

[Nate]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:79.0) Gecko/20100101 Firefox/79.0

Steps to reproduce:

Typed "outlook.com" in address bar and then hit Enter key.

Actual results:

Nothing happened.

Expected results:

Firefox should have gone to https://outlook.live.com/mail/0/inbox (the automatic Microsoft redirect). Behavior started a couple weeks ago. It happens every day and with other manually-typed urls that used to work.

Comment 1

[Nate]

Forgot to mention that when I type the url into the address bar a second time it always works. It's the first time that produces no action.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Comment 3

[Alice0775 White]

I can reproduce the issue if login status of the site was remembered.

Comment 4

[Daniel B.]

I’ve been experiencing this bug a lot at least a month now. I have a self-hosted Discourse forum (not publicly accessible) that is affected. There’s nothing in the console. The bug only manifests intermittently, but when it does, I sometimes have to restart the browser to make the page load again. I think new tabs are affected more, but it also happens in existing tabs (that already have pages loaded).

The Discourse Service Worker script is based on Google Workbox. It does not rely on external script files. It is used to intercept HTTP requests and to display notifications.

Comment 5

[zvonimir.erdelja]

I am having this problem consistently if the first URL I open after starting Firefox is mail.google.com. It happens only the first time after Firefox is started, not in a new window or tab, but after a restart of Firefox. I can even open many tabs and windows after the restart and the first tab in which I navigate somewhere, if I navigate to mail.google.com, it fails. After that, in that tab and in all others it works.
Other URL mostly work also the first time.

I have these errors in the console, but I have them as soon as Firefox starts, before clicking anything, I don't know whether they are relevant:

[Exception... "Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED) [nsIAppStartup.secondsSinceLastOSRestart]"  nsresult: "0x80004001 (NS_ERROR_NOT_IMPLEMENTED)"  location: "JS frame :: resource:///modules/BrowserGlue.jsm :: _collectStartupConditionsTelemetry :: line 1682"  data: no] BrowserGlue.jsm:1682:9
    _collectStartupConditionsTelemetry resource:///modules/BrowserGlue.jsm:1682
    BG__onFirstWindowLoaded resource:///modules/BrowserGlue.jsm:1806
    BG_observe resource:///modules/BrowserGlue.jsm:946
    _delayedStartup chrome://browser/content/browser.js:2108
    _delayedStartup self-hosted:1161
Unknown category for SetEventRecordingEnabled: fxmonitor
TypeError: PrecompiledScript.executeInGlobal: Argument 1 is not an object. ExtensionContent.jsm:568:25
Key event not available on some keyboard layouts: key=“r” modifiers=“accel,alt” id=“key_toggleReaderMode” browser.xhtml
Key event not available on some keyboard layouts: key=“i” modifiers=“accel,alt,shift” id=“key_browserToolbox” browser.xhtml
debuggee 'resource://devtools/shared/base-loader.js:289' would run builtin-modules.js:196:11

I have the problem both in Linux Mint and in Windows 10.

Interestingly enough, if I open the network monitor, it shows one request to google with Status: blocked. This could be the key.

Comment 6

[Andrew Sutherland [:asuth] (he/him)]

I think this was probably due to DocumentChannel aborting loads on re-parenting and was fixed in late 2020. Alternately, some of our ServiceWorker mitigations may have helped since we handle problems with the navigation failing to load by bypassing the ServiceWorker. Do you still experience anything like this?

Comment 7

[BugBot [:suhaib / :marco/ :calixte]]

Redirect a needinfo that is pending on an inactive user to the triage owner.
:jari, since the bug has recent activity, could you have a look please?

For more information, please visit BugBot documentation.

Comment 8

[Jari Jalkanen [:jari]]

Seems like this is not reproduceable anymore with 138.0.1 or nightly. Please reopen if the issue is actually still present.