SECOND tab do not closing . any other (1,3,4..) is ok. it started when FF96 upd
Categories
(Firefox :: Tabbed Browser, defect)
Tracking
()
People
(Reporter: verylogin, Unassigned, NeedInfo)
Details
Attachments
(1 file)
|
43.11 KB,
image/png
|
Details |
problem illustration
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:96.0) Gecko/20100101 Firefox/96.0
Steps to reproduce:
using multiple tabs, I try to close second tab
Actual results:
but it can't.
any other tabs closing correctly (1,3,4..)
so, if I want close second tab I need close first and then again first.
Expected results:
just fix it. I want close my tabs in any order.
|
||
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Tabbed Browser' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
it happening after FF was in background while some apps was in fullscreen mode
|
||
Comment 3•2 years ago
|
||
Hi,
Thanks for your report. DId you have another ff window with a website in fullscreen? Or what kind of app did you have in fullscreen mode?(zoom for example?)
I haven't been able to reproduce on my end using latest beta, release and nightly buids, in windows 10. Feel free to attach a video too if you're able to, to make sure i'm not missing any steps.
Thanks!
Clara
(In reply to Clara Guerrero from comment #3)
Hi,
Thanks for your report. DId you have another ff window with a website in fullscreen? Or what kind of app did you have in fullscreen mode?(zoom for example?)
I haven't been able to reproduce on my end using latest beta, release and nightly buids, in windows 10. Feel free to attach a video too if you're able to, to make sure i'm not missing any steps.
Thanks!
Clara
Starcraft Brood War ))
|
||
Comment 5•2 years ago
|
||
Apologies for leaving this issue stale for this long.
As Clara, I can't reproduce the issue regardless of version used: 96.0, 102.3.0esr, 105.0.3, 106.0 RC, 107.0a1 (2022-10-12). My first assumption would be that something in your profile is causing this.
If this issue is still reproducible on your side(preferably using some of the latest versions), could you please try with a new profile and in safe mode? If the safe mode/ new profile do not reproduce the problem, but your profile does, then please attach a copy of your about:support.
I'm closing it as WFM for the time being, please reopen based on the above line result
Description
•