www.fiverr.com - Drag and drop hover effect not displayed when trying to send a file/image to a user
Categories
(Web Compatibility :: Site Reports, defect, P2)
Tracking
(Webcompat Priority:P2, Webcompat Score:6, firefox-esr115 wontfix, firefox-esr140 wontfix, firefox143 wontfix, firefox144 wontfix, firefox145 fix-optional)
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | wontfix |
| firefox-esr140 | --- | wontfix |
| firefox143 | --- | wontfix |
| firefox144 | --- | wontfix |
| firefox145 | --- | fix-optional |
People
(Reporter: ctanase, Unassigned)
References
(Depends on 1 open bug, Regression, )
Details
(5 keywords, Whiteboard: [webcompat-source:web-bugs][webcompat:sightline])
User Story
platform:windows,mac,linux impact:significant-visual configuration:general affects:all branch:release diagnosis-team:dom user-impact-score:300
Attachments
(3 files)
Environment:
Operating system: Windows 10
Firefox version: Firefox 141.0/142/144
Steps to reproduce:
- Go to https://www.fiverr.com/
- Log in via any social options. (e.g. Google)
- Go to messages (inbox) and open an existing conversation (if you don't have any - search for services and contact a user directly, you will have to send him a message and return to the conversation in the inbox).
- Click and drag a file from your computer and hold it over the chat.
Expected Behavior:
The Drag and drop hover effect is displayed "Drop files here".
Actual Behavior:
The Drag and drop hover effect is not displayed.
Notes:
- The Drag and drop itself works, just the hover effect is missing
- Reproduces regardless of the status of ETP
- Reproduces in firefox-nightly, and firefox-release
- Does not reproduce in chrome
Created from https://github.com/webcompat/web-bugs/issues/172271
| Reporter | ||
Comment 1•5 months ago
|
||
| Reporter | ||
Updated•5 months ago
|
| Reporter | ||
Updated•5 months ago
|
Updated•5 months ago
|
Comment 2•5 months ago
|
||
Go to messages and open an existing conversation (or contact somebody - search for services and contact the user directly).
Can you elaborate on this one? I created two accounts to test conversation but I can't see how I can start conversation between the two.
| Reporter | ||
Comment 3•5 months ago
•
|
||
I'm not sure if you can do that, unless one of your accounts has a gig/service posted on the website.
You could search for example "Logo design" and click on the user that actually provides this service, there's a "Contact me" button.
Comment 4•5 months ago
|
||
I'm not able to reproduce this mainly because I'm struggling to actually drag and drop an image onto a chat box. Perhaps if you have some more detailed reproduction steps I can try to follow closely.
| Reporter | ||
Comment 5•5 months ago
|
||
@keithamus if you've contacted somebody already, just open the chat from the messages (https://www.fiverr.com/inbox). Then just click and drag an image/file from your computer and hold it over the chat. An overlay "Drop files here" should appear while holding the file over the chat.
My screen rec in case you've missed it: https://bugzilla.mozilla.org/show_bug.cgi?id=1984283#c1
Updated•5 months ago
|
Comment 6•5 months ago
•
|
||
I tried to click "contact me" from a user, which I randomly selected from the search result list of "Logo Design", as comment 3 suggested.
However, I've not managed to find a "draggable element" in a chat, either on Chrome or Firefox.
I did see "cursor" differences between Chrome and Firefox though.
In Firefox, when I dragged a file to a chat, there was a "not-allowed" cursor.
In Chrome, when I dragged a file to a chat, there was a "copy drag feedback cursor, which has "localized term of "copy" + copy badge. When I released the mouse to drop the file, the file was opened in a new tab. Still, it wasn't draggable to the chat. That is, * didn't see "Drop files here".
Here is the link I used.
Hi Calin Tanase, do you see the same behavior as I if you visit the link I provided? If you still can reproduce with other users, can you share the links for those users? Thank you.
| Reporter | ||
Comment 7•5 months ago
•
|
||
Correct me if I'm wrong but you've tested this on the chat window that appears on the left when you click "Contact me"? If thats the case, I could reproduce the behavior you've described but what I meant in my initial comment is to access the conversation from the inbox. (https://www.fiverr.com/inbox)
(or contact somebody - search for services and contact the user directly).
This was meant in case your account doesn't have an existing conversation, you still have to send a message to the user so the conversation appears in the inbox. Sorry if the description created confusion.
Edit: I've updated the STR
Comment 8•4 months ago
|
||
Is it all AI assistants or am I going to ping real people without having real intent to interact? 🥴
Comment 9•4 months ago
|
||
(In reply to Kagami Rosylight [:saschanaz] (they/them) from comment #8)
Is it all AI assistants or am I going to ping real people without having real intent to interact? 🥴
@Calin Tanase ,
Sorry for another ping. Do you have insights to Kagami's question above, which is also my question as well?
Updated•4 months ago
|
| Reporter | ||
Comment 10•4 months ago
|
||
I think its a mix of both. The user can see your message but you might get an automated reply.
Comment 11•4 months ago
|
||
Adding needs-contact to attempt reaching out to fiverr, which would be preferred over spamming innocent people. :/
Updated•4 months ago
|
Comment 12•4 months ago
|
||
onDragHandler(e) {
e.preventDefault();
const t = (0, ne.h) ('dataTransfer.types', e) ||
[];
1 === t.length &&
'Files' === t[0] &&
this.toggleDragModeOn()
}
Comment 13•4 months ago
|
||
We're failing the above code because we have:
e.dataTransfer.types = [0: "application/x-moz-file", 1: "Files"]
Chrome has
e.dataTransfer.types = [0: "Files"]
Updated•4 months ago
|
Updated•4 months ago
|
Comment 14•4 months ago
|
||
Set release status flags based on info from the regressing bug 1290688
:nika, since you are the author of the regressor, bug 1290688, could you take a look?
For more information, please visit BugBot documentation.
Comment 15•4 months ago
|
||
I'm not sure this is the correct diagnosis. IIRC we were always exposing "application/x-moz-file" even before the changes in bug 1290688.
I think the fix being proposed right now in bug 1993095 might work. I don't have time to dig deeper or figure out next steps right now though. I've left more comments on that bug.
Updated•4 months ago
|
Comment 16•4 months ago
|
||
Yeah, by marking it as being regressed I more just meant that bug 1290688 made the conscious choice to keep "application/x-moz-file" in.
Comment 17•2 months ago
|
||
This is still an issue on Firefox Nightly 147.0a1(2025-11-13)
Description
•