Closed
Bug 1410009
Opened 8 years ago
Closed 11 months ago
[gmailcom] The border and the text for "Drop Files Here" area is still present
Categories
(Core :: DOM: Copy & Paste and Drag & Drop, defect)
Core
DOM: Copy & Paste and Drag & Drop
Tracking
()
People
(Reporter: obotisan, Unassigned)
References
Details
(Whiteboard: [platform-rel-Google][platform-rel-Gmail])
Attachments
(3 files)
[Affected versions]:
- Nightly 29.0a1 - Nightly 58.0a1
[Affected platforms]:
- Ubuntu 16.04 x 64
- Windows 10 x 64
- macOS 10.13 Mac OS X 10.11
[Steps to reproduce]:
1. Access your gmail account
2. Click "Compose"
3. Drag and drop a few files (that are pictures, videos) in the "Drop Files Here" area.
4. Without actually dropping them, pull them away, outside the browser. Try to do that a few times.
[Expected result]:
- The "Drop Files Here" area is not highlighted (active) anymore.
[Actual result]:
-The border and the text for "Drop Files Here" area is still present, sometimes even after you close the New Message window.
[Regression range]:
- I don't think it's a regression. I managed to reproduce the bug even with an old version of Nightly from 2014-01-02.
[Additional notes]:
- You can find attached a video and a picture with the issue.
Reporter | ||
Comment 1•8 years ago
|
||
Reporter | ||
Comment 2•8 years ago
|
||
I will attach the screenshot with the issue again in .png format.
Comment 3•8 years ago
|
||
status-firefox59:
--- → ?
Comment 4•8 years ago
|
||
I can reproduce this issue in Firefox 58-60 for OSX 10.13. It takes quite a few times of hovering the file to get the issue to appear. I wasn't able to reproduce in Chrome 64 for OSX.
platform-rel: --- → ?
Whiteboard: [platform-rel-Google][platform-rel-Gmail]
Updated•3 years ago
|
Severity: normal → S3
Comment 6•11 months ago
|
||
Closing this as WFM as it is no longer reproducible on our latest Nightly 132.0a1 (2024-09-32) using WIN 10 and macOS 11.
Status: NEW → RESOLVED
Closed: 11 months ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•