Clicking Dropdown Input List Item Doesn't Work Unless Long Press
Categories
(GeckoView :: IME, defect, P3)
Tracking
(Not tracked)
People
(Reporter: ekager, Unassigned)
References
()
Details
(Whiteboard: [geckoview:2023?])
Steps to reproduce
- Go to https://www.laposte.fr/particulier/outils/trouver-un-point-d-envoi-de-colis-ou-de-retrait?query=94140
- Tap in the area where the zip code
94140
is displayed - A list of one item appears with
94140 Alfortville, France
- Tap this item
Expected behavior
- The input changes with this value
- A map is displayed on this city
Actual behavior
Nothing is happening
Emily Edit: If you long press on the drop down item, it seems to work, but that seems wrong.
Device information
- Android device: Pixel 2, Android 10
- Fenix version: Firefox Preview Nightly (Nightly 200603 06:00) Build 21550609 GV78, can also reproduce on Fenix Beta GV 75
Note:
- This is working in chrome
- Expanding the area for the suggestion (padding,margin) so it takes more screen real estate and is not anymore close to the input, and the selection is working.
- Initial webcompat report https://github.com/webcompat/web-bugs/issues/53520
Comment 1•4 years ago
|
||
Mike, what is the priority for this for Fenix?
Comment 2•4 years ago
|
||
Original Fenix issue: https://github.com/mozilla-mobile/fenix/issues/11215
Comment 3•4 years ago
|
||
laposte.fr is a surprisingly popular site (Top 1500, according to Alexa). Also, this is using what appears to be the Google Maps Autocomplete API, which is probably all over the web. I would consider this to be pretty important to fix.
Comment 4•4 years ago
|
||
Hi John, per comment 3, can you please spend time on investigating these and suggesting the next step first? Thanks.
Comment 5•4 years ago
|
||
Sure, I'll take a look. Keep NI for tracking.
Comment 6•4 years ago
|
||
According to [1], it seems more like an android widget issue. Redirect to Widget: Android component.
[1] https://github.com/webcompat/web-bugs/issues/53520#issuecomment-638536331
Updated•4 years ago
|
Comment 8•4 years ago
|
||
Not really. You can check the old implementation (not for long though) with widget.disable-native-theme-for-content=false
, and refreshing the page. The bug still repros there.
Plus those controls are not natively styled, so it's not like the theme should have an effect anyway.
I think running mozregression
on this is the best next step to figure out fwiw.
Updated•4 years ago
|
Updated•4 years ago
|
Updated•2 years ago
|
Comment 9•2 years ago
|
||
Makoto says this bug might be related to bug 1511157, which is blocked on spec issue https://github.com/w3c/uievents/issues/202.
Comment 10•2 years ago
|
||
Moving some input bugs to the new GeckoView::IME component.
Comment hidden (spam) |
Updated•8 months ago
|
Updated•5 months ago
|
Description
•