The drag-able button from the Traffic pop-up of Google Maps cannot be dragged using touchscreen
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P3)
Tracking
()
People
(Reporter: danibodea, Unassigned)
References
(Blocks 1 open bug)
Details
Note
- The "time of day" draggable button should be draggable using the touchscreen.
Affected versions
- Nightly v64.0a1 from 2019-02-27
- Beta V66.0b11
Affected platforms
- Windows 10 on a touchscreen device
- I don't have other OSes on a touchscreen device, so I could not test those.
Steps to reproduce
- Reach Google Maps: https://www.google.com/maps
- Move the visible map area over a more populated area.
- Tap on the "Hamburger" menu button (3 horizontal lines at the left of the search input box)
- Tap on the "Traffic" button.
- Tap on the "Live Traffic" drop-down from the left side of the Traffic pop-up displayed at the bottom of the map area.
- Switch selection to "Typical Traffic"
- Attempt to drag the "dime of the day" selector.
Expected result
- The selector is correctly and easily dragged.
Actual result
- The selector cannot be caught and dragged using the touchscreen.
Additional notes
- This issue does not occur on the EDGE browser.
- This issue also occurs on the Chrome browser.
- This issue does not occur when using a mouse or a touch-pad.
- The selector can be moved by tapping on the screen instead.
Comment 1•6 years ago
|
||
Hi Mike,
Can your team help investigate what's up here? :)
Assignee | ||
Updated•6 years ago
|
Updated•5 years ago
|
Comment 2•5 years ago
|
||
Sorry for missing this. I've just verified that Firefox is behaving the same as Chrome, which just means this is a site bug. You can just tap the time and the slider will jump to it.
Feel free to reach out to Google Maps about this issue.
Reporter | ||
Comment 3•5 years ago
|
||
It is true, this issue also occurred on Chrome, but it did not occur on EDGE. (Info in Additional Notes section of bug description) What would be an explanation for this?
Comment 4•5 years ago
|
||
What would be an explanation for this?
Not sure. But since Edge is switching to Chromium, they will inherit this bug.
Given that Chrome has majority market share, if we're matching their behavior I don't see this as a bug worth spending time on (especially since tapping works as expected).
Description
•