Closed Bug 1383573 Opened 7 years ago Closed 7 years ago

Browser start displays loading halo (busy)

Categories

(Core :: DOM: Events, defect, P1)

Product:
Core
Component:
DOM: Events
Version:
56 Branch
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox-esr52 --- unaffected
firefox54 --- unaffected
firefox55 --- unaffected
firefox56 + unaffected

People

(Reporter: jmjjeffery, Assigned: stone)

References

Details

(Keywords: regression) 

On start of the browser the UI opens find but there is a Windows Loading 'Halo' displayed that seems to hang for some time. 

You can still click to 'Restore Previous Session' and all works find.  Its just that loading 'Halo' is bothersome in that one could think the browser is hung during startup.

MozRegression points to:
Bug 1351148 Part8: Revise browser_1008559_anchor_undo_restore.js to continue the test after processing the mouse event. r=smaug.
Blocks: 1351148
Keywords: regression
[Tracking Requested - why for this release]: Regression
Severity: normal → major
Has Regression Range: --- → yes
Has STR: --- → yes
status-firefox54: --- → unaffected
status-firefox55: --- → unaffected
status-firefox56: --- → affected
status-firefox-esr52: --- → unaffected
tracking-firefox56: --- → ?
Version: Trunk → 56 Branch
Flags: needinfo?(sshih)
Priority: -- → P1
Assignee: nobody → sshih
Flags: needinfo?(sshih)
Track 56+ as new regression.
tracking-firefox56: ? → +
Using the latest tinderbox (hourly) win32 build running on Win10 x64 I am no longer seeing the 'loading halo' .

No idea which patch or possible backout fixed the problem.

Leaving this open for now in case there is still investigation on-going by the developers
I think this bug has the same cause as bug 1383485 and it's a regression of bug 1351148.
Moving 56-status to unaffected as bug 1351148 was backed-out from 56.
status-firefox56: affected → unaffected
Blocks: 1390044
Stone told me this should have been fixed in bug 1351148. He will verify again then close it.
I think this is resolved after relanding the patches of bug 1351148. Verified on nightly with pref'ed on and can't reproduce it.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.