New issue
Advanced search Search tips

Issue 648232 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Sep 2016
Cc:
dtapu...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Bug with oninput event in Chrome 53.x only

Reported by gilpe...@gmail.com, Sep 19 2016 
Please read this really small thread -> http://stackoverflow.com/questions/39563036/oninput-event-not-working-anymore

Other people confirmed this bug, so I think you should take a look cause it happened with me too only in version 53.x not in earlier ones.

Comment 1 by elawrence@chromium.org, Sep 19 2016

Components: -UI>Settings Blink>Input
Labels: -Proj-MaterialDesign-WebUI
Status: Untriaged (was: Unconfirmed)
I expect this is working as intended.

http://blog.chromium.org/2016/08/chrome-53-beta-shadow-dom.html

https://bugs.chromium.org/p/chromium/issues/detail?id=520519

Comment 2 Deleted

Comment 3 Deleted

Comment 4 by gilpe...@gmail.com, Sep 19 2016 

Yeah, it's bad news, really bad news. If I want to compile the 53.x version only to overcome this new "feature", do you know exactly where I need to change the code? Is there any chrome switch which I can use to disable this "feature"?

Comment 5 by dtapu...@chromium.org, Sep 22 2016

Status: WontFix (was: Untriaged)
I responded to the stack overflow issue. You can use execCommand.

document.execCommand("insertText", false, "foo");

This is an intended consequence of  issue 520519 .

Comment 6 by dtapu...@chromium.org, Sep 22 2016

Cc: dtapu...@chromium.org

Comment 7 by dtapu...@chromium.org, Sep 22 2016 

 Issue 648228  has been merged into this issue.

Comment 8 by dtapu...@chromium.org, Sep 27 2016

Labels: Hotlist-Input-Dev
►

Sign in to add a comment