Search Issue Tracker

Won't Fix

Won't Fix in 6000.6.X

Votes

0

Found in

6000.0.70f1

6000.3.11f1

6000.4.0f1

6000.5.0a9

6000.6.0a1

Issue ID

UUM-137533

Regression

No

Moving a Tab to a floating window fails when floating windows are docked next to each other

Editor Window Management

-

Steps to reproduce:

  1. Open the attached project
  2. Dock the Main Editor window so it takes the left half of the screen
  3. Add 2 new Inspector Tabs to the existing Inspector Tab
  4. Convert the added windows into floating windows
  5. Dock the floating windows so that one takes the bottom right quarter of the screen and the other - the top right quarter of the screen
  6. From the Main Editor window, start dragging the initial Inspector tab
  7. Try moving the tab to the top right floating window - Observe that the tab can be moved to the floating window
  8. Try moving the tab to the bottom right floating window

Actual results: The tab can't be moved to the bottom right floating window, instead it is inserted between the floating windows

Expected results: The tab can be moved to any floating window

Reproducible with versions: 6000.0.70f1, 6000.3.11f1, 6000.4.0f1, 6000.5.0a9, 6000.6.0a1

Tested on (OS): Windows 11, macOS 26.3.1

  1. Resolution Note:

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

  2. Resolution Note (6000.6.X):

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.