This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 973
Infinite loading spinner when detaching a loading tab (sometimes) #13803
Labels
priority/P4
Minor loss of function. Workaround usually present.
QA/test-plan-specified
release-notes/include
wontfix
Comments
petemill
added
the
0.22.x-single-webview
Issue first seen on single-webview build against v0.22.x branch
label
Apr 11, 2018
Seems fixed with 0.22.700 |
This was referenced May 3, 2018
Verified on Windows x64
|
Reproduced it twice on Mint 18.3 x64 using the following STR:
|
I know why this is happening, and it is happening on the current release too. We are handling load 'start' and 'finish' (and 'error') in the renderer, and attaching the status property to the window frame, but if a load-finish comes to the old window (before the tab has finished moving to the new one), then the new frame object will not receive the updated load status. A solution to this would be to move load status to the browser state (tab object), or check for the current status when the frame is finally loaded in the destination window. |
petemill
added
the
priority/P4
Minor loss of function. Workaround usually present.
label
May 7, 2018
petemill
modified the milestones:
0.22.x Release 3 (Beta channel),
Backlog (Prioritized)
May 7, 2018
petemill
removed
0.22.x-single-webview
Issue first seen on single-webview build against v0.22.x branch
regression
labels
May 7, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
priority/P4
Minor loss of function. Workaround usually present.
QA/test-plan-specified
release-notes/include
wontfix
Steps to Reproduce
Actual result:
Load spinner of tab in new window does not stop when load is complete
Expected result:
Load spinner reflects current status of load
Reproduces how often:
~20%, depends on timing
Brave Version
about:brave info:
0.22.106
Reproducible on current live release:
Unknown
The text was updated successfully, but these errors were encountered: