UI not functioning on non-primary profile when multiple windows are opened
Categories
(Firefox :: Tabbed Browser, defect)
Tracking
()
People
(Reporter: matthewrbowker.bugs, Unassigned, NeedInfo)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:107.0) Gecko/20100101 Firefox/107.0
Steps to reproduce:
- Create a non-default profile.
- Open a second browser window by right-clicking on a tab then choose "Move Tab" > "Move to new window"
- Open a new tab.
- Attempt to interact with the UI. (In my case, I tried to close the primary tab using the close button and middle click. I also attempted to click into the address bar ack the hamburger menu on the right.)
Please note that changing tabs and the bookmark bar do work.
Actual results:
There is no response in the UI.
Expected results:
I should be able to interact with the entire UI.
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Toolkit::Startup and Profile System' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•3 years ago
|
||
(In reply to Matthew Bowker from comment #0)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:107.0) Gecko/20100101 Firefox/107.0
Steps to reproduce:
- Create a non-default profile.
Can you expand on this step? How exactly did you create the non-default profile. I'm assuming that for the subsequent steps you opened Firefox using that non-default profile but how did you do that?
| Reporter | ||
Comment 3•3 years ago
|
||
Yes, gladly!
To create new profile:
- Open a fresh instance of Nightly.
- Visit "about:profiles"
- Click "Create a new profile"
- Click "Continue"
- Enter profile name.
- Click "Done"
To launch this profile:
- Open default instance of Nightly.
- Visit "about:profiles"
- Under the profile I want to use, click "Launch profile in new browser"
As part of my standard workflow, I generally have 2-3 profiles open at once.
| Reporter | ||
Comment 4•3 years ago
|
||
After a Nightly update, this issue has gone away. I don't know exactly what happened, but I believe we can call this "fixed."
Comment 5•3 years ago
|
||
The severity field is not set for this bug.
:dao, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•3 years ago
|
Description
•