Bug 483029 - Firefox On Plasma 6 Wayland Dragging and Rearranging A Bookmark Auto Opens A Bookmark Above It
Summary: Firefox On Plasma 6 Wayland Dragging and Rearranging A Bookmark Auto Opens A ...
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 6.0.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-03-09 19:54 UTC by WadamT
Modified: 2024-03-14 17:08 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.1


Attachments
clip demo (3.54 MB, video/mp4)
2024-03-09 19:54 UTC, WadamT
Details
Firefox issue (242.45 KB, video/webm)
2024-03-12 04:14 UTC, Shubham Arora
Details

Note You need to log in before you can comment on or make changes to this bug.
Description WadamT 2024-03-09 19:54:01 UTC
Created attachment 166824 [details]
clip demo

SUMMARY
When you drag and rearrange a bookmark in Firefox, be it in 'other bookmark' or at home page, the moment you drop the bookmark, Firefox auto opens a bookmark above or below it. This happens only in  Wayland session, not in X11.


STEPS TO REPRODUCE
1.  Run KDE 6 on Wayland session also Firefox on Wayland
2.  Try drag and rearrange a bookmark in 'other bookmark'
3.  See error

OBSERVED RESULT
The moment you drop the rearranged bookmark, Firefox auto opens a bookmark above or below it

EXPECTED RESULT
Firefox doesn't auto open the bookmark

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux wih KDE 6
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.7.0
Firefox Version: 123.0.1 (64-bit)

ADDITIONAL INFORMATION
Also reported at Firefox bugzilla - https://bugzilla.mozilla.org/show_bug.cgi?id=1881784
Comment 1 Shubham Arora 2024-03-10 19:29:46 UTC
Able to reproduce the issue and basedon the comments in mozilla tickets seems plasma 6 wayland specific.
Comment 2 Nate Graham 2024-03-11 23:58:31 UTC
Cannot reproduce in Plasma 6 wayland with Firefox in native Wayland mode, either with bookmarks in the "Other Bookmarks" folder or any other folder on the bookmarks toolbar. Is it running on XWayland when you're able to reproduce the issue?
Comment 3 Shubham Arora 2024-03-12 04:14:59 UTC
Created attachment 167012 [details]
Firefox issue

I am able to reproduce it. See attachment for evidence.

Window Protocol	wayland : for firefox version 125.0a1

Operating System: EndeavourOS 
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.7.0
Kernel Version: 6.7.8-arch1-1.1-g14 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 6800HS with Radeon Graphics
Memory: 14.9 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: ROG Flow X13 GV301RA
System Version: 1.0
Comment 4 duha.bugs 2024-03-12 16:52:46 UTC
I can reproduce on Plasma 6.0.1 (Wayland), but not on Git master (Wayland). So this is likely already fixed, but I don't know which commit.
Comment 5 Jon 2024-03-12 18:59:31 UTC
Related to / duplicate of: https://bugs.kde.org/show_bug.cgi?id=482687 maybe?

FWIW I see all cursor interaction with Firefox being 30-ish pixels off, but only on one computer, and only when I snap firefox to left or right half of the screen.  If I maximize then snap left or right all my cursor interactions are correct.

Looks like this MR might have fixed it: https://invent.kde.org/plasma/kwin/-/merge_requests/5382
Comment 6 Nate Graham 2024-03-13 17:15:30 UTC
Could be. If so, the issue should be fixed in Plasma 6.0.2. Can anyone still reproduce the issue in that version?
Comment 7 WadamT 2024-03-13 18:51:02 UTC
Tested on Arch Linux with Plasma 6.0.2. I can still reproduce this bug.
Comment 8 Nate Graham 2024-03-13 19:12:10 UTC
Ok, thanks. Marking as fixed in Plasma 6.1 for now, but if anyone can pinpoint the commit that fixed it, we can consider backporting it.
Comment 9 WadamT 2024-03-14 11:57:06 UTC
This bug is no longer happening in 6.0.2 after a restart. Sorry for my previous comment.
Comment 10 Shubham Arora 2024-03-14 17:08:21 UTC
No longer reproducible for  me as well. Tested on 2 devices.