Unloaded tabs cannot be dragged from icon until after they have been loaded
Categories
(Core :: DOM: Copy & Paste and Drag & Drop, defect)
Tracking
()
People
(Reporter: rdoghi, Assigned: sefeng211)
References
(Blocks 2 open bugs, Regression)
Details
(Keywords: regression)
Attachments
(4 files)
Found in
- 134.0a1 (2024-11-13)
Affected versions
- 134.0a1 (2024-11-13)
- Beta 133.0b7
- Release 132
- Esr 128
Preconditions
Have a Previous session with a lot of tabs.
Affected platforms
- all
Steps to reproduce
- Launch Firefox and Restore the previous session.
- Before the Tabs have a chance to load try to move them around.
Expected result
- The user should be able to move the tabs around even if they have not started to load their content.
Actual result
- Sometimes the user has to click a tab again in order to move them while the first click starts to load the content from that tab.
Please note that this issue does not happen at a 100% repro rate.
You can see this issue at around second 20 in the attached video
Regression range
Not a Regression.
Updated•1 year ago
|
STR:
- Create a tab and unload it by right-clicking > Unload Tab or from
about:processesor close and restore the window. - Drag the unloaded tab from the icon. On Windows this must be done before the loading animation finishes.
Expected:
Unloaded tab can be dragged from the icon.
Actual:
Tab does not respond to dragging from the icon until after it has loaded and drag is performed again.
Windows is more forgiving, allowing drag to work if the cursor is held still until after the loading animation finishes but this is not the case on Linux.
Vertical tabs in the collapsed state are especially affected since the icon dominates the draggable area. This is also the case with horizontal pinned tabs but they load on startup by default so are not normally affected. Rearranging many unloaded tabs requires "waking up" each tab first or dragging from the edges of the tab.
First appeared in version 57 when tabs changed to Photon design.
Regression window:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=52285ea5e54c73d3ed824544cef2ee3f195f05e6&tochange=63e261ce8cb04c913d2e6b19ea451b7078d24dc1
Possibly regressed by Bug 1349555.
Updated•1 year ago
|
Comment 4•1 year ago
|
||
:dao, since you are the author of the regressor, bug 1349555, could you take a look?
For more information, please visit BugBot documentation.
Comment 5•11 months ago
|
||
with
<div id="parent" draggable="true">
<div id="children">children</div>
</div>
it seems like if the "children" gets replaced between mousedown and dragstart, the drag would not start(when click inside children's display area), demo attached
I don't know if this is desired behavior, but in chromium the drag would start normally
for the issue of unloaded tabs, looks like it's setting tab label and icon when loading, leads to behavior described above
add pointer-events: none; to both .tab-icon-image and .tab-label-container seems fix it for tab
Comment 6•11 months ago
|
||
Moving this to Core based on comment 5.
| Assignee | ||
Comment 7•11 months ago
|
||
NI myself to take a look, I vaguely remember seeing something similar.
| Assignee | ||
Comment 9•11 months ago
|
||
So we prevent the drag from starting because the node is disconnected, hence this check fails. Maybe we should update the gesture content to the parent when that happens. I am trying to come up a patch.
| Assignee | ||
Comment 10•10 months ago
|
||
Updated•10 months ago
|
Comment 11•10 months ago
|
||
Comment 13•10 months ago
|
||
| bugherder | ||
Comment 14•10 months ago
|
||
Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.
Updated•10 months ago
|
| Reporter | ||
Comment 15•10 months ago
|
||
Verified as fixed in our latest Nightly build 137.0a1 (2025-02-23)
| Assignee | ||
Updated•6 months ago
|
Description
•