input element with associated datalist should show autocomplete options
Categories
(Fenix :: Browser Engine, defect)
Tracking
(Not tracked)
People
(Reporter: jonatan, Unassigned)
References
(Depends on 1 open bug)
Details
Steps to reproduce:
Suggestions for input elements don't render when using Fenix 111.1.0 from an android phone.
- Go to https://webxr.sh/dropdowns#datalist
- Enter text in the input fields
Actual results:
No suggestions render when using Fenix on my phone (111.1.0)
Options do render when using firefox on my ubuntu computer (111.0.1), or using all other browsers I've tested.
Expected results:
Options for the input should have rendered.
I did my best to search for related issues, but I've never tried to use this site before. ... That I remember.
I did find similar issues, but they seemed to suggest that the issue was working on Fenix, and not on ... Gecko? Whatever.
This issue is definitely still active on Fenix 111.1.0.
Comment 2•2 years ago
|
||
The severity field is not set for this bug.
:cpeterson, could you have a look please?
For more information, please visit auto_nag documentation.
Is there any way I can do more to help this bug report be processed?
I've looked at the similar bug talking about Gecko. The severity there seems to be S3, with a developer putting it as S4 then upgrading it.
Using inputs with datalist options as an autocomplete select-like input seems to be not uncommon, and works in all other browsers. I have live sites that work fine on all major browsers except firefox for android, where you cannot fill in certain forms because the option elements don't render.
I suppose this technically makes it S3 in severity, assuming the ability to fill in basic forms rendered without javascript is considered non-critical. However, from my perspective, it feels frustrating that native form elements not rendering isn't considered a higher priority. Still, I understand that there's a lot to do.
I'm going to try setting up a firefox dev platform over the weekend and help out. Anyone wanting to point me in a direction to avoid common pitfalls when trying to do such are welcome.
Updated•1 year ago
|
Comment 5•11 months ago
|
||
This problem is still present in the latest version (119.1.1) of Firefox for android
Description
•