Closed Bug 1557275 Opened 5 years ago Closed 5 years ago

[wayland] reordering tabs within a ff window doesn't work

Categories

(Core :: Widget: Gtk, defect, P2)

69 Branch
defect

Tracking

()

RESOLVED DUPLICATE of bug 1527976

People

(Reporter: luis.pabon, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:69.0) Gecko/20100101 Firefox/69.0

Steps to reproduce:

Ubuntu 19.04, firefox-trunk from mozilla ppa (69.0a1hg20190604r476795-0ubuntu0.19.04.1~umd1), sway 1.1.

  • env MOZ_ENABLE_WAYLAND=1 firefox-trunk
  • Open a bunch of tabs
  • Try to drag them around to reorder (within the same window)

Actual results:

Nothing.

Expected results:

Tabs can be reordered.

This is not the same as https://bugzilla.mozilla.org/show_bug.cgi?id=1527976 - that bug is about detaching a tab into a new window (which also doesn't work).

Component: Untriaged → Widget: Gtk
Product: Firefox → Core
Blocks: wayland
Priority: -- → P3

I've seen this as well, it doesn't occur all the time (and might take a while to stop working). I THINK how I've triggered it in the past is to switch to external monitors (dock) and then dragging stopped working. May also have something to do with multiple windows (I typically have at least two ff windows open).

I think it's related to wrong droparea size which is stored in nsWindow. I spent some time with this and going to look at it more.

Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: P3 → P2

Btw. this is the same bug as 1527976 - the drag does not start because due to broken drag area coordinates.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---

This one has regressed upon upgrade to 69.0a1hg20190620r479697-0ubuntu0.19.04.1~umd1.

Keywords: regression
Status: REOPENED → RESOLVED
Closed: 5 years ago5 years ago
Keywords: regression
Resolution: --- → DUPLICATE

It is a sway issue where drag and drop randomly stops working. Restoring ticket state as it was before.

You need to log in before you can comment on or make changes to this bug.