Long press on Back and Forward browser buttons intermittently doesn't cause navigation
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox86 | --- | affected |
People
(Reporter: bytesized, Unassigned)
Details
I'm not really sure exactly what's causing this or how exactly to reproduce it, so I'm just going to describe the experience I'm having. I have a pinned YouTube tab that gets restored on browser start and which I use to listen to music. I frequently hold the back button to see and navigate to songs I have listened to recently.
Sometimes, I click another video from the back or the forward button, and no page navigation occurs. This seems to coincide with this message in the Browser Toolbox:
Error: Warning processing windowTypes: This property is deprecated global.min.js:250
a moz-extension://42eb9201-457e-454c-bd93-1f738f9c44f6/global.min.js:250
I typed moz-extension://42eb9201-457e-454c-bd93-1f738f9c44f6 in the location bar, and I see this filename amongst the output: onepassword4@agilebits.com.xpi, so I am guessing that somehow my 1Password extension is involved.
The problem is a bit mysterious. Once I've clicked the button maybe a half dozen times, the page does eventually navigate. I have not yet experienced the problem on any other tab than my pinned YouTube tab.
I'm using Firefox Nightly 86.0a1 (2021-01-08) (64-bit) on Windows 10.
| Reporter | ||
Comment 1•5 years ago
|
||
Hmm. I'm going to remove this from the webextension component, because I think that error message is unrelated. I think I'm actually seeing that whenever I switch to the Browser Toolbox window, not when I experience the problem with the back button. If I arrange the Firefox and Toolbox windows so I can see both at once (rather than switching back and forth), I no longer get one of these messages per problem occurrence.
| Reporter | ||
Comment 2•5 years ago
|
||
Since this problem is intermittent, I'm going to post some details that I don't really know are related to the problem. I was getting no error messages on the multiple back button failures. But right after the problem resolved itself (i.e. when the page actually navigated), I saw these messages, which I do not normally see when visiting the same page:
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIWorkerDebugger.postMessage] worker-transport.js:39
send resource://devtools/shared/transport/worker-transport.js:39
onPacket resource://devtools/server/devtools-server-connection.js:355
receiveMessage resource://devtools/shared/transport/child-transport.js:68
TypeError: can't access property "requestIdleCallback", this.contentWindow is null
PictureInPictureChild.jsm:453:9
onIntersection resource://gre/actors/PictureInPictureChild.jsm:453
onIntersection self-hosted:1176
(Async: IntersectionCallback)
registerVideo resource://gre/actors/PictureInPictureChild.jsm:376
handleEvent resource://gre/actors/PictureInPictureChild.jsm:326
Fe https://www.youtube.com/s/player/9f996d3e/player_ias.vflset/en_US/base.js:255
x0 https://www.youtube.com/s/player/9f996d3e/player_ias.vflset/en_US/base.js:5064
wAa https://www.youtube.com/s/player/9f996d3e/player_ias.vflset/en_US/base.js:5084
u0 https://www.youtube.com/s/player/9f996d3e/player_ias.vflset/en_US/base.js:5053
create https://www.youtube.com/s/player/9f996d3e/player_ias.vflset/en_US/base.js:8635
playerBootstrap https://www.youtube.com/watch?v=HIfFA8-RaHQ:20
<anonymous> https://www.youtube.com/watch?v=HIfFA8-RaHQ:20
Promise rejected after context unloaded: Actor 'Conduits' destroyed before query 'RuntimeMessage' was resolved
content_script_bundle.js:95
action moz-extension://4b3998f8-f92d-41fc-a9e6-350d61c117ae/dist/content_script_bundle.js:95
TypeError: can't access property "removeEventListener", this.contentWindow is nullPictureInPictureChild.jsm:569:5
stopTrackingMouseOverVideos resource://gre/actors/PictureInPictureChild.jsm:569
didDestroy resource://gre/actors/PictureInPictureChild.jsm:195
| Reporter | ||
Comment 3•5 years ago
|
||
To additionally clarify, when this is problem happens, the URL bar does not change, nor does the selected entry in the "back button drop down". So Firefox is indeed misbehaving here, rather than this being purely YouTube weirdness.
Comment 4•5 years ago
|
||
When this happens, is your Browser Toolbox usually open?
| Reporter | ||
Comment 5•5 years ago
|
||
Recently it has been open, because I've been trying to track down what's going on. But I opened the Toolbox because this was happening. It does happen without the Toolbox open.
| Reporter | ||
Comment 6•5 years ago
|
||
It just happened again, and I once again saw those PiP errors that I posted above. I don't see these in my toolbox history at any other point other than when this happens.
| Reporter | ||
Comment 7•5 years ago
•
|
||
It happened again. This time I saw the TypeError: can't access property "removeEventListener", this.contentWindow is null PiP error message, but not the other ones.
Also, I now think the way that I fix it is consistent, contrary to what I previously thought. The behavior always seems to follow this pattern:
- I hold the back or forward button and pick the page I want to navigate to
- Nothing happens
- This seems to be repeatable indefinitely
- At some point, I accidentally do a short press on the button rather than long one
Still no page navigationSometimes page navigation happens at this point, sometimes not.- I long press and pick a page one more time
- Now page navigation succeeds
| Reporter | ||
Updated•5 years ago
|
| Reporter | ||
Comment 8•5 years ago
|
||
Yeah, I think I have pretty much confirmed the way I can fix the issue when it happens. I just did a long press 50 times, each resulting in no navigation. Then a short press, which didn't navigate. The next long press resulted in navigation.
| Reporter | ||
Comment 9•5 years ago
|
||
Ah, I was asked on Slack if I am using Fission, and it appears that I am. Perhaps this is Fission related?
Comment 10•5 years ago
|
||
Randell says this is a dupe of bug 1684310.
| Reporter | ||
Comment 11•5 years ago
|
||
I can confirm that I was seeing it quite frequently with Fission on, but I haven't seen it so far with Fission off.
Description
•