Process Manager: clicking x in tab does not close tab in 127.0.2
Categories
(Toolkit :: Performance Monitoring, defect)
Tracking
()
People
(Reporter: mgryan, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:127.0) Gecko/20100101 Firefox/127.0
Steps to reproduce:
run Mazilla Firefox 127.0.2
Press SHIFT-CONTROL
In Process Manager tab at top of screen click on the 'x'
Actual results:
Tab does not close.
Expected results:
Tab should close.
Right click on the same tab, pull down to "close tab"
Tab does close correctly.
Underlying functionality works, GUI interface is broken.
Priority level: there is an easy work-around (the above), but if the user
doesn't think of it, he's stuck. He'll have to close Firefox.
Comment 1•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Tabbed Browser' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Hello, thank you for the bug report!
Managed to reproduce this issue on:
- Firefox Nightly 129.0a1;
- Firefox 128.0;
Tested and reproduced on:
- Ubuntu 22;
- macOS 14;
- Windows 10;
Setting as NEW so the developers can have a look.
Updated•1 year ago
|
Comment 3•1 year ago
|
||
I just tried reproducing in Nightly (129.0a1 (2024-07-03) (64 bits)) on Mac and couldn't reproduce. So either there's a step I didn't understand, or it doesn't reproduce for me.
When the problem occurs, is there any error reported in the browser console?
I am now unable to reproduce this bug in same version (127.0.2 for Windows).
I don't know what's changed--other than I just opened Firefox. I will try again after Firefox has been active for some time.
I didn't look at the Browser console when I initially observed the bug. I should have--sorry
I apologise, I seem to have made a mistake. I mistakenly closed the processes and not the tabs themselves when first testing. Re-tested both Firefox Nightly 130.a1 and Firefox 129.0b2 and I can confirm that the issue is not reproducible on my side either, as the tabs close without any problems whilst pressing Shift+CTRL/CMD. No errors in the browser console as well. Setting the status back to UNCOMFIRMED until further confirmation is received. I’m very sorry for the confusion.
Comment 6•1 year ago
|
||
Given comment 4 and comment 5, I'm going to resolve this as INCOMPLETE.
mgryan, if you see this again, we can reopen.
Description
•