tabbed browsing can be broken (tab switching not working, documents not loading)
Categories
(Firefox :: Tabbed Browser, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox71 | - | fix-optional |
People
(Reporter: aryx, Unassigned)
References
(Regression)
Details
(Keywords: regression, steps-wanted)
Attachments
(1 file)
25.67 KB,
text/plain
|
Details |
Firefox 71.0a1 20191010214019 64-bit on Windows 8.1
After the update to 71.0a1 20191010214019 got installed (updated from 20191010214019), the contents of active tabs remained empty and hitting Ctrl+R didn't change it. Switching tabs by clicking on them didn't do anything except the tab getting the focus ring.
Menu Help > Troubleshooting Information opened that tab in the background, dragging it onto the taskbar successfully opened it as a tab in a new window with content shown.
The issue couldn't be reproduced with a new profile and also not with a session set up (including session restore) and upgraded to that Nightly version.
Closing the affected profile and launching it again made the issue go away.
Failures from the console:
TypeError: aBrowser.webProgress is undefined 2 tabbrowser.js:1893:7
updateBrowserRemoteness chrome://browser/content/tabbrowser.js:1893
_setupEventListeners chrome://browser/content/tabbrowser.js:5275
_insertBrowser chrome://browser/content/tabbrowser.js:2364
getRelatedElement chrome://browser/content/tabbrowser-tabs.js:1978
set selectedIndex chrome://global/content/elements/tabbox.js:553
set selectedItem chrome://global/content/elements/tabbox.js:579
_selectNewTab chrome://global/content/elements/tabbox.js:749
on_mousedown chrome://global/content/elements/tabbox.js:345
on_mousedown chrome://browser/content/tabbrowser-tab.js:357
handleEvent chrome://global/content/customElements.js:468
TypeError: aBrowser.webProgress is null tabbrowser.js:1893:7
updateBrowserRemoteness chrome://browser/content/tabbrowser.js:1893
_setupEventListeners chrome://browser/content/tabbrowser.js:5275
get loadContext chrome://global/content/elements/browser-custom-element.js:467
construct chrome://global/content/elements/browser-custom-element.js:1280
connectedCallback chrome://global/content/elements/browser-custom-element.js:395
_insertBrowser chrome://browser/content/tabbrowser.js:2364
getRelatedElement chrome://browser/content/tabbrowser-tabs.js:1978
set selectedIndex chrome://global/content/elements/tabbox.js:553
set selectedItem chrome://global/content/elements/tabbox.js:579
_selectNewTab chrome://global/content/elements/tabbox.js:749
on_mousedown chrome://global/content/elements/tabbox.js:345
on_mousedown chrome://browser/content/tabbrowser-tab.js:357
handleEvent chrome://global/content/customElements.js:468
NS_ERROR_UNEXPECTED: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIScriptSecurityManager.getLoadContextContentPrincipal] browser-custom-element.js:1278
construct chrome://global/content/elements/browser-custom-element.js:1278
connectedCallback chrome://global/content/elements/browser-custom-element.js:395
_insertBrowser chrome://browser/content/tabbrowser.js:2364
getRelatedElement chrome://browser/content/tabbrowser-tabs.js:1978
set selectedIndex chrome://global/content/elements/tabbox.js:553
set selectedItem chrome://global/content/elements/tabbox.js:579
_selectNewTab chrome://global/content/elements/tabbox.js:749
on_mousedown chrome://global/content/elements/tabbox.js:345
on_mousedown chrome://browser/content/tabbrowser-tab.js:357
handleEvent chrome://global/content/customElements.js:468
TypeError: browser.webProgress is null tabbrowser.js:2378:7
TypeError: aBrowser.frameLoader.remoteTab is null 2 E10SUtils.jsm:786:18
Comment 1•5 years ago
|
||
[Tracking Requested - why for this release]:
We can't ship with something like this.
Comment 2•5 years ago
|
||
(In reply to Sebastian Hengst [:aryx] (needinfo on intermittent or backout) from comment #0)
Firefox 71.0a1 20191010214019 64-bit on Windows 8.1
After the update to 71.0a1 20191010214019 got installed (updated from 20191010214019), the contents of active tabs remained empty and hitting Ctrl+R didn't change it. Switching tabs by clicking on them didn't do anything except the tab getting the focus ring.
All of these 3 build IDs are the same - which one did you update from and which one did you update to ?
Comment 3•5 years ago
|
||
Also, can you add about:support from the affected profile? I wonder if we could ask QE to do some exploratory testing.
Reporter | ||
Comment 4•5 years ago
|
||
All of these 3 build IDs are the same - which one did you update from and which one did you update to ?
about:support's update history lists an update attem at 2019-10-11 12:34 UTC which failed ("patch apply failed"). It should have been 2019101009... but I remember hitting the elevated permission prompt for the updater later twice the day it occurred. The nightly binary runs 1-2 profiles here. Trying to reproduce the issue with downloading the update in both profiles didn't succeed (one profile detects the other as running). Will report if I see this bug or the installer issue again.
Updated•5 years ago
|
Updated•5 years ago
|
Comment 6•5 years ago
|
||
It doesn't seem like this is reproducible currently, but if anyone gets STR, then I can take a look.
Updated•5 years ago
|
Comment 7•5 years ago
|
||
Untracking and marking as fix-optional as we don't have other reports and no clear STR on this one, if we find STRs and a patch materializes we could evaluate an uplift.
Updated•4 years ago
|
Updated•2 years ago
|
Description
•