Open Bug 1985207 Opened 1 year ago Updated 1 year ago

Tabs can't be moved on top of VSCode

Categories

(Core :: Widget: Win32, defect)

Firefox 142
defect

Tracking

()

People

(Reporter: nicolast, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:142.0) Gecko/20100101 Firefox/142.0

Steps to reproduce:

Dragging an existing tab out of an existing firefox window to its own new window, which happens to land on top of Visual Studio Code (1.103.1) on Firefox 142.0 in Windows 11 makes the new tab window immediately disappear behind the VSCode window.

Actual results:

The firefox tab, now a new firefox window, is hidden behind the existing vscode window.

Expected results:

The firefox tab should appear on top of vscode, as it was dragged on top of it.

I've seen similar bugs like https://bugzilla.mozilla.org/show_bug.cgi?id=1417276 and https://bugzilla.mozilla.org/show_bug.cgi?id=1598915 which claims it was fixed in 132, but it's still not working.

This comment from Ray seems most relevant https://bugzilla.mozilla.org/show_bug.cgi?id=1598915#c12

Can provide a screen capture of the issue if required.

Thanks.

Component: Untriaged → Widget: Win32
Product: Firefox → Core
See Also: → 1598915, 1417276
Severity: -- → S4

Do you know if this is a new issue, or has it existed for a while? If it's new, running mozregression would help us figure out what caused it.

Also, if it's not too much trouble a screen capture would be helpful. Thanks!

Flags: needinfo?(nicolast)

Hi Greg, it's existed for as long as I've used Firefox, so probably 6 months to a year now.

https://www.dropbox.com/scl/fi/k0ejifa45acs1mrso7ocu/firefox.mkv?rlkey=i43w8an00zvgfw1lgu5dwkkqe&e=1&st=j5uie1xg&dl=0 has a screen capture showing dropping the tab above vscode working fine, but dropping the tab anywhere on vscode will push it behind.

Thanks!

Flags: needinfo?(nicolast)

Confirmed this, and mozregression doesn't help; this has probably been broken ever since bug 1598915 was fixed.

Status: UNCONFIRMED → NEW
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.