Prompt blocks image we are supposed to copy
Reported by
jidanni@gmail.com,
Jun 27 2018
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.25 Safari/537.36 Example URL: Steps to reproduce the problem: Encounter a CAPTCHA with the image below the entry box What is the expected behavior? What went wrong? Here we observe we are trying to fill in a CAPTCHA, alas chromium's form filler selector prompts are blocking the image that we are trying to read. The only way to fill it in is to click on another part of the page, then write down the numbers on a piece of paper, and then click on the entry box and type them in. Yes you might say the page is wrong for putting the image below the entry box, when everyone is supposed to know that is where the browser needs to show its defaults. But isn't the browser supposed to be more flexible than the page? If you need to reproduce the problem, you need to have already sent two letters to the city government on https://hello.gov.taipei/ . Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? No Does this work in other browsers? N/A Chrome version: 68.0.3440.25 Channel: n/a OS Version: Flash Version:
,
Jun 27 2018
jidanni@ - Thanks for filing the issue...!! Could you please provide sample credentials for url: https://hello.gov.taipei/ or any other sample url to test the issue from TE-end. This will help us in triaging the issue further. Thanks...!!
,
Jun 27 2018
Simple: In an incognito window browse https://accounts.google.com/ you will see chromium showing you a list of accounts you have hopefully previously used. Now imaging this list is covering up a CAPTCHA that we are supposed to copy into the box.
,
Jun 27 2018
imaging->imagine.
,
Jun 27 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
,
Jun 30 2018
,
Jul 18
Able to reproduce the issue on Mac 10.13.3, Win-10 and Ubuntu 14.04 using chrome reported version #68.0.3440.25 and latest canary #69.0.3494.0. This is a non-regression issue as it is observed from M60 old builds. Hence, marking it as untriaged to get more inputs from dev team. Thanks...!! |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by vamshi.kommuri@chromium.org
, Jun 27 2018