New issue
Advanced search Search tips

Issue 765657 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Incognito mode and basic browser auth window crash input text behaviour

Reported by alesha.d...@gmail.com, Sep 15 2017

Issue description

Steps to reproduce the problem:
Simple server that asks basic auth with default browser window (in desktop browser it looks like on screenshot1). After auth simple html page with one text input will be rendered.

1. Open new tab in incognito mode
2. Be sure that auth window appeares
3. Enter correct login and password
4. When target page is rendered tap on input (focus) and try to enter some cymbols.

What is the expected behavior?
Text cursor appeares and every keypress change input value 

What went wrong?
Cursor doesn't appears
Input value doesn't change after key press

If you make events subscription with addEventListenet to input you will notice that 'keyup' and 'keydown' events work correct, but browser doesn't fire 'input' event.

Did this work before? N/A 

Chrome version: 60.0.3112.107  Channel: n/a
OS Version: 6.0.1
Flash Version: 

Very strange that:
1. ASUS Zenpad Z380KL allows to type numbers in landscape
2. Lenovo A5000 doesn't allow to type anything in portrait but if you rotate smartphone to landscape you will be able to enter numbers

Actualy, this problem can be reproduced without incognito mode. You just need to clear cache totally and do all the steps. You can reload page and the problem will gone.

I faced this problem when user tried to use my project first time and couldn't enter value. He reloaded the page and this solved the problem.

After some research i decided to reproduced it in incognito and i think this is the same problem
 
screenshot1.png
33.4 KB View Download
Components: -Blink Blink>Editing

Comment 2 by yosin@chromium.org, Sep 19 2017

Components: -Blink>Editing Blink>Editing>IME
Labels: Needs-Feedback
NextAction: 2017-10-03
Summary: NEEDS_FEEDBACK Incognito mode and basic browser auth window crash input text behaviour (was: Incognito mode and basic browser auth window crash input text behaviour)
Could you provide HTML file to reproduce this issue?

Is this caused by HTML file which only have INPUT element without SCRIPT?

Does screenshot in #c1 relate to this issue? It seems it is screenshot of
Windows.




You can find index.html in attached files.

Problem doesn't depends on JavaScript. In attached index.html you can remove event subscriptions and nothing will change.

Screenshot IS NOT RELATE to the issue, it's just example of basic authorization window cause i don't know how it's called and how to describe to you what i'm talking about.

If you need i can attach zip file with simple nodejs server (1.35 kb without node_modules) to reproduce auth.
index.html
534 bytes View Download
Project Member

Comment 4 by sheriffbot@chromium.org, Sep 19 2017

Cc: yosin@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "yosin@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by yosin@chromium.org, Sep 22 2017

Cc: -yosin@chromium.org
NextAction: ----
Status: Available (was: Unconfirmed)
Summary: Incognito mode and basic browser auth window crash input text behaviour (was: NEEDS_FEEDBACK Incognito mode and basic browser auth window crash input text behaviour)
Thanks for providing HTML file.
Mark Available to help people to pick this up.

Comment 6 by yosin@chromium.org, Sep 22 2017

Labels: -Pri-2 Pri-3
Lower to Pri-3 since real world usage of basic authentication is low.
Windows authentication use this component too
Project Member

Comment 8 by sheriffbot@chromium.org, Sep 24

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
We've implemented another kind of auth 6 monthes ago ¯_(ツ)_/¯
This ticket is not important for me
Status: Available (was: Untriaged)

Sign in to add a comment