1984342 - Toolbar buttons becoming unresponsive (leftover movingtab attribute)

Status: RESOLVED FIXED

(Firefox :: Toolbars and Customization, defect)

Description

[numanron]

Steps to reproduce:

Sometimes the buttons on toolbar (like back, forward, reload, hamburger menu) become unresponsive; clicking it or even hovering will do nothing.
It's not a consistant bug; seems to happen when I reload a tab and switch to an other tab before the previous lab reloaded. The bug sometimes go away when I switch around tabs a couple times. I was able to reproduce this bug with all the extensions disabled.
This is the first Firefox version I experienced this.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Firefox for Android::General' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Mike Conley (:mconley) (:⚙️)]

Hi numanron,

While the browser is responsive, are you able to visit about:support and click "Copy Text to Clipboard", and then paste the contents here as a comment in this bug (or in an attachment to the bug)?

Comment 3

[numanron]

Attachment: about support

(In reply to Mike Conley (:mconley) (:⚙️) from comment #2)
> Hi numanron,
> 
> While the browser is responsive, are you able to visit about:support and click "Copy Text to Clipboard", and then paste the contents here as a comment in this bug (or in an attachment to the bug)?

Here you go.
``

Comment 4

[:Gijs (he/him)]

(In reply to numanron from comment #0)

Steps to reproduce:

Sometimes the buttons on toolbar (like back, forward, reload, hamburger menu) become unresponsive; clicking it or even hovering will do nothing.

When this happens, does using equivalent keyboard shortcuts still work? (ctrl-r for reload or alt-left/right arrow for back/fwd)

It's not a consistant bug; seems to happen when I reload a tab and switch to an other tab before the previous lab reloaded. The bug sometimes go away when I switch around tabs a couple times.

When you're in the broken state and trying to get out, are you switching tabs via keyboard or mouse, and/or do both work?

Comment 5

[numanron]

(In reply to :Gijs (he/him) from comment #4)

(In reply to numanron from comment #0)

Steps to reproduce:

Sometimes the buttons on toolbar (like back, forward, reload, hamburger menu) become unresponsive; clicking it or even hovering will do nothing.

When this happens, does using equivalent keyboard shortcuts still work? (ctrl-r for reload or alt-left/right arrow for back/fwd)

Yes, keyboard shortcuts still work.

It's not a consistant bug; seems to happen when I reload a tab and switch to an other tab before the previous lab reloaded. The bug sometimes go away when I switch around tabs a couple times.

When you're in the broken state and trying to get out, are you switching tabs via keyboard or mouse, and/or do both work?

I'm switching tabs with mouse; sometimes even the tabs become unresponsive; actually when that happens it happens to that one specific tab I was on when encountering the bug.
Switching to an other app and back to Firefox might also fix the issue.

Comment 6

[:Gijs (he/him)]

Thanks! Do you ever drag tabs, either to reorder them or to detach them into their own window? And do you ever intentionally multi-select tabs - and any chance that you're doing some of this before the breakage happens?

Comment 7

[Itiel]

Is the content area responsive during that time? Or is it only the chrome area stuck?

Comment 8

[numanron]

(In reply to :Gijs (he/him) from comment #6)

Thanks! Do you ever drag tabs, either to reorder them or to detach them into their own window? And do you ever intentionally multi-select tabs - and any chance that you're doing some of this before the breakage happens?

I don't really do that and especially not before this bug happens. Btw. the address bar also becomes unresponsive.

Comment 9

[numanron]

(In reply to Itiel from comment #7)

Is the content area responsive during that time? Or is it only the chrome area stuck?

As far as I experienced the content area works fine.

Comment 10

[Emilio Cobos Álvarez [:emilio]]

If when this happens dragging a tab around fixes it, it would be a version of bug 1955112 or so

Comment 11

[numanron]

(In reply to Emilio Cobos Álvarez (:emilio) from comment #10)

If when this happens dragging a tab around fixes it, it would be a version of bug 1955112 or so

I've just tried this and indeed when it bugs out dragging the tab fixes it instantly.

Comment 12

[Andrew]

Yeah, as Alice pointed out this looks to be the exact same bug I experienced.

Comment 14

[daveman0011]

I seem to have this same issue since upgrading to Firefox 142.0, on Windows 11. It's happened twice-- Clicking the toolbar buttons does not work, and clicking the address bar does not work. (I have not yet attempted keyboard shortcuts or dragging tabs.)

Comment 15

[Ciprian.Enache]

Confirm this is also present in 142.0 on Windows 10 i.e. clicking the toolbar buttons does not work, and clicking the address bar does not work.

Comment 16

[Mike Conley (:mconley) (:⚙️)]

For people who are still experiencing this, when the browser enters this state, the Browser Console might contain some vital information to help us determine what's happening.

On Windows and Linux, the console can be opened by hitting Ctrl-Shift-J (I believe this should still work even if the toolbar is unresponsive).
On macOS, the console can be opened by hitting Cmd-Shift-J.

What we're looking for is text in the console that might have anything to do with the toolbar or tab strip. Errors are helpful, but if you're not sure and you're willing, the entire console might contain useful information.

Comment 17

[Stephen Thompson [:sthompson]]

Bug 1984870 describes getting into this state just by closing tabs

Comment 18

[numanron]

(In reply to Mike Conley (:mconley) (:⚙️) from comment #16)

For people who are still experiencing this, when the browser enters this state, the Browser Console might contain some vital information to help us determine what's happening.

On Windows and Linux, the console can be opened by hitting Ctrl-Shift-J (I believe this should still work even if the toolbar is unresponsive).
On macOS, the console can be opened by hitting Cmd-Shift-J.

What we're looking for is text in the console that might have anything to do with the toolbar or tab strip. Errors are helpful, but if you're not sure and you're willing, the entire console might contain useful information.

I might be wrong but it seems to be that this only happens at certain sites, one of them is steamcommunity.com
Only one error message is logged on those pages, it appears at every page refresh and adds +1 repeats every time the bug activates:
NotFoundError: No such JSProcessActor 'BrowserToolboxDevToolsProcess'

Comment 19

[Ed]

See also https://www.reddit.com/r/firefox/comments/1n01m0i/firefox_being_buggy/.

Comment 20

[jmc787]

Yep just signed up as I was seeing this a lot last night when moving between tabs, FF 142 Win11
Dragging a tab to a different position fixed it

Comment 21

[igobento]

(In reply to Mike Conley (:mconley) (:⚙️) from comment #2)

Hi numanron,

While the browser is responsive, are you able to visit about:support and click "Copy Text to Clipboard", and then paste the contents here as a comment in this bug (or in an attachment to the bug)?

I am experiencing two issues intermittently, but consistently: 1) the address bar/URL becomes grayed out and the web address cannot be clicked/changed. 2) tabs and tab groups become froze, do not collapse and expand as normal, and just generally don't work.

09:07:12.589
NS_ERROR_NOT_AVAILABLE:
09:07:14.077
NS_ERROR_NOT_AVAILABLE:
09:10:05.708
NS_ERROR_NOT_AVAILABLE:
09:10:12.315
NS_ERROR_NOT_AVAILABLE:
09:11:39.006
NS_ERROR_NOT_AVAILABLE:
09:12:01.724
NS_ERROR_NOT_AVAILABLE:
09:12:22.021
NS_ERROR_NOT_AVAILABLE:
09:13:40.805
NS_ERROR_NOT_AVAILABLE:
09:13:44.529
NS_ERROR_NOT_AVAILABLE:
09:14:07.036
NS_ERROR_NOT_AVAILABLE:
09:14:08.470
NS_ERROR_NOT_AVAILABLE:
09:18:15.688
NS_ERROR_NOT_AVAILABLE:
09:18:33.556
NS_ERROR_NOT_AVAILABLE:
09:18:34.233 Assertion failed: Giving up waiting for the tab closing animation to finish (bug 608589) tabbrowser.js:4792:21
09:19:09.020
Error: Form history is disabled, only remove operations are allowed
update resource://gre/modules/FormHistory.sys.mjs:1075
addToFormHistory resource:///modules/UrlbarUtils.sys.mjs:1170
pickResult resource:///modules/UrlbarInput.sys.mjs:1356
pickElement resource:///modules/UrlbarInput.sys.mjs:1044
handleNavigation resource:///modules/UrlbarInput.sys.mjs:795
handleCommand resource:///modules/UrlbarInput.sys.mjs:732
handleKeyNavigation resource:///modules/UrlbarController.sys.mjs:357
_on_keydown resource:///modules/UrlbarInput.sys.mjs:4848
maybeDeferEvent resource:///modules/UrlbarEventBufferer.sys.mjs:159
_on_keydown resource:///modules/UrlbarInput.sys.mjs:4847
handleEvent resource:///modules/UrlbarInput.sys.mjs:696

09:19:09.222
NS_ERROR_NOT_AVAILABLE:
09:19:10.384 The resource at “https://csp.withgoogle.com/csp/gws/fff” was blocked by OpaqueResponseBlocking. Reason: “nosniff is true and mimeType is an opaque-blocklisted MIME type or its essence is 'text/plain'”.
09:21:21.803
NS_ERROR_NOT_AVAILABLE:
09:21:33.943
NS_ERROR_NOT_AVAILABLE:
09:21:33.945
NS_ERROR_NOT_AVAILABLE:
09:22:54.777
NS_ERROR_NOT_AVAILABLE:
09:24:57.218
Unknown property ‘-moz-border-radius’. Declaration dropped.

Comment 22

[Mike Conley (:mconley) (:⚙️)]

Thanks for all your help, everybody. We think we've narrowed in on a culprit (we strongly suspect that fixing bug 1982933 will fix this). Version 142.0.1 will be released soon, which we believe should alleviate the issue.

For those on the Beta channel, Firefox 143.0b4 and greater also has the fix. If anybody here is using Beta, we'd love to hear if the problem has gone away for you!

Comment 23

[Dianna Smith [:diannaS]]

Marking as fixed by bug 1982933 and 142.0.1 is now live. feel free to comment if you are still having the issue.