Open Bug 1891720 Opened 1 year ago Updated 1 year ago

🦊 🐧Drag and drop to Firefox results in Chinese symbols like these 㜱㜸㤱㠰㤴㜶㔰㌲㔰㄰🐞

Categories

(Core :: DOM: Copy & Paste and Drag & Drop, defect)

Firefox 124
Unspecified
Linux
defect

Tracking

()

UNCONFIRMED

People

(Reporter: jordanov.borislav, Unassigned, NeedInfo)

Details

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

Steps to reproduce:

Dragging and dropping text/links from Telegram to Firefox address bar or new tab results in hard mess (unidentified symbols). I believe it must be something related to the encoding.

I tried drag and drop to a terminal and other programs and the text drops as it's supposed to be.

I tried drag and drop from other programs to Firefox and the text is also as it's supposed to be.

First I thought the fault was in Telegram but then I tried dragging and dropping text from Telegram to other apps and it seems to be alright.

This behaviour can be observed on a stable (not bleeding edge) Linux kernel. Snap is purged, Firefox with snap is purged too so I just use apt:

https://packages.mozilla.org/apt mozilla/main

Actual results:

Chinese symbols appear

Please watch this short screen recording - https://www.reddit.com/r/firefox/comments/1c4t1ox/drag_and_drop_to_firefox_results_in_chinese/

Expected results:

The text I dragged should appear

The Bugbug bot thinks this bug should belong to the 'Core::DOM: Copy & Paste and Drag & Drop' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → DOM: Copy & Paste and Drag & Drop
Product: Firefox → Core

Dragging and dropping text/links from Telegram to Firefox address bar

How to do that? I cannot drag anything "out" of Telegram under Wayland.

(In reply to Andre Klapper from comment #2)

Dragging and dropping text/links from Telegram to Firefox address bar

How to do that? I cannot drag anything "out" of Telegram under Wayland.

I'm using KDE.

OS: Unspecified → Linux

Yep, I didn't specify on purpose. That's all I could help you with. I'll live with the bug until I figure out why it happens or someone figures before me and it eventually gets fixed.

I tried to reproduce this bug on Kubuntu, but I cannot with the preinstalled Firefox nor Nightly build built by myself.

jordanov.borislav: Which distribution do you use? And can you reproduce this with a beta build which is directly built by mozilla?

Flags: needinfo?(jordanov.borislav)
You need to log in before you can comment on or make changes to this bug.