Closed Bug 1745626 Opened 3 years ago Closed 3 years ago

Loading indicator is displayed forever in some page

Categories

(Core :: DOM: Core & HTML, defect, P1)

Product:
Core
Component:
DOM: Core & HTML
Version:
Firefox 97
Type:
defect

Tracking

()

Status:
VERIFIED FIXED
Milestone:
97 Branch
Tracking Flags:
Tracking Status
firefox-esr91 --- unaffected
firefox95 --- unaffected
firefox96 --- unaffected
firefox97 --- verified
firefox98 --- verified

People

(Reporter: mix5003, Assigned: yulia)

References

(Regression,
URL
)

Details

(Keywords: regression)

Attachments

(2 files)

20211212_092112.mp4
(deleted), video/mp4
Details
Bug 1745626 - Dynamic import should always try to unblock onload event in DOM context; r=jonco
(deleted), text/x-phabricator-request
Details
Attached video 20211212_092112.mp4 (deleted) —

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

Steps to reproduce:

open https://svelte.dev/docs#tick

Actual results:

after page loaded, load indicator still show as loading

Expected results:

it should show favicon after page loaded

The Bugbug bot thinks this bug should belong to the 'Core::Networking' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Networking
Product: Firefox → Core

Able to reproduce issue. From mozregression:
Bug 1311726 - Split ScriptLoader into ScriptLoader and ModuleLoader; r=jonco

Differential Revision: https://phabricator.services.mozilla.com/D132683

URL: https://svelte.dev/docs#tick
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: regression
Regressed by: 1311726
Has Regression Range: --- → yes
Assignee: nobody → ystartsev

I am not sure how this is triggering the behavior, so I wasn't able to make a test that replicates it. But this fix reverts a change in the module loader refactor that is the source of the issue.

I would expect that the onload event is well tested, but there might be another event that the UI is listening for. I am not sure what that might be.

Set release status flags based on info from the regressing bug 1311726

status-firefox95: --- → unaffected
status-firefox96: --- → unaffected
status-firefox97: --- → affected
status-firefox-esr91: --- → unaffected
Severity: -- → S3
Severity: S3 → --
Priority: -- → P1
Priority: P1 → --
Pushed by ystartsev@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/75b4ceb13878 Dynamic import should always try to unblock onload event in DOM context; r=jonco
Severity: -- → S3
Status: NEW → ASSIGNED
Component: Networking → DOM: Core & HTML
Priority: -- → P1
Whiteboard: [necko-triaged]
Whiteboard: [necko-triaged]

https://hg.mozilla.org/mozilla-central/rev/75b4ceb13878

Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox97: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → 97 Branch
Flags: qe-verify+

I was able to reproduce the issue on Win10x64 using build 97.0a1(20211211213843).
Verified as fixed on Win10 and Ubuntu 20.4 using Beta 97.0b2(20220111185943) and NB 98.0a1(20220113093336).

Status: RESOLVED → VERIFIED
status-firefox97: fixed → verified
status-firefox98: --- → verified
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: