Fields on e-aadhaar website are not functioning properly
Reported by
aj.jaswa...@gmail.com,
Mar 21 2018
|
|||||||||
Issue descriptionExample URL: https://eaadhaar.uidai.gov.in/ Steps to reproduce the problem: 1. Open https://eaadhaar.uidai.gov.in/ 2. Choose "I have Aadhaar" 3. Try fill field "Enrolment ID/Aadhaar Number" or "Pin Code" What is the expected behavior? Numbers should be entered as expected. What went wrong? Digits are entered in reverse for "Enrolment ID/Aadhaar Number" Digits are not appearing for "Pin Code" Does it occur on multiple sites: No Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? N/A Chrome version: 65.0.3325.109 Channel: stable OS Version: Android 7.0.0 Flash Version:
,
Mar 23 2018
aj.jaswanth@ -- Thanks for reporting this issue. But, the URL provided by you (https://eaadhaar.uidai.gov.in/) doesn't seems to be accessible. It always gives 'This site can’t be reached' error. Could you please verify the URL provided. Also, request you to provide the device details where the issue is reproduced. Thanks!
,
Mar 23 2018
The url is valid. I can access it. It could be a network issue?
,
Mar 23 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 23 2018
I was using Redmi Note 4. This could be an issue with the website itself. However, it works fine in desktop Chrome. It also works fine in Safari on iOS.
,
Mar 23 2018
,
Mar 26 2018
Tested the issue in Android and able to reproduce the issue. Similar behavior is observed since Chrome #60.0.3072.0 Steps Followed: 1. Launched the Chrome Browser. 2. Navigate to the URL: https://eaadhaar.uidai.gov.in/ 3. Select the radio button "Choose "I have Aadhaar" 4. Try entering numbers in the fields "Enrolment ID/Aadhaar Number" or "Pin Code" 5. Observed that upon entering numbers, numbers are not displayed. Chrome versions tested: 60.0.3072.0, 65.0.3325.109(Stable), 67.0.3379.0(Canary) OS: Android 8.1, Android 7.0.0 Android Devices: Pixel XL, Samsung J7 This seems to be a Non-Regression issue as same behavior is seen since M60. Untriaged for further input's on this issue. Please navigate to below link for log's and screen cast-- go/chrome-androidlogs/824142 Note: 1. This issue is not observed in Desktop. 2. Issue is not observed on FireFox mobile version. However, same behavior is seen in Microsoft Edge and Opera browsers. Thanks!
,
Mar 30 2018
,
Apr 5 2018
I don't seem to be able to access the page either. Anyone can download the page and attach it to this bug? Presumably it would happen the same for the offline page.
,
Apr 5 2018
Yes. It is not accessible for me as well. I'll attach the page once it is available.
,
Apr 12 2018
Any news for the page? Were you able to access it and download the page? Are you still able to repro the issue?
,
Apr 12 2018
Hi. Found that the page is Geo restricted. It is only available in India. Attaching the recursively offline downloaded one.
,
May 3 2018
Confirmed locally - the page is doing something strange in JS (disabling JS makes it work) that doesn't work with the Android IME. Needs more investigation. Dave, do you know off hand what differences might exist between IME events and real keyboards?
,
May 3 2018
Android IME doesn't generate keydown/keyup/keypress events.
,
Oct 25
,
Oct 25
it is still not working. Any update and how come Mozilla Firefox is working with android IME
,
Oct 25
,
Oct 25
Another user reports in issue 898009 and issue 898102 that this issue only occurs on arm64 devices and not arm32, which seems unlikely but if true is really bizarre (especially since chrome still ships as 32-bit even on arm64 devices). It also apparently repros in WebView the same way. Android IMEs are indeed not guaranteed to generate key events since the IME generally commits text regions directly. If the JS is just assuming there will be key events then the page is broken (see issue 118639 ) and the site owners need to fix it..
,
Oct 25
er, issue 898099 there, not 898009.
,
Oct 25
Likely there is a keyboard attached in the report on the arm64 (even a BT keyboard would make this work). Agree this is likely a site issue.
,
Oct 25
Ok if you think its a site issue then how come mozilla firefox is working great on same devices. I logged 898099 and 898102 issue. You can check the video over there with mozilla firefox.
,
Oct 25
And the thing about arm64 and arm32. I have samsung on7 device which is armeabi-v7 and this particular site work fine in that (webview and chrome) but when it comes to my one plus 5 it doesn't. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by pnangunoori@chromium.org
, Mar 22 2018