Pressing enter in input triggers blur event
Reported by
i...@relaylabs.co,
Jan 3 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36 Steps to reproduce the problem: 1. Visit this page: https://jsfiddle.net/c22pez5z/ 2. Focus the form input 3. Press enter and observe that a native blur event is recorded What is the expected behavior? Pressing enter in a form input does not trigger a blur event in other browsers (tested in Firefox and Safari). It seems this behaviour may have changed in Chrome at some point. What went wrong? This issue was reported in React (https://github.com/facebook/react/issues/11826) as it is causing issues with React's synthetic event system. Did this work before? Yes Unknown Chrome version: 63.0.3239.108 Channel: stable OS Version: OS X 10.13.2 Flash Version:
,
Jan 3 2018
I believe this is likely caused by: https://chromium.googlesource.com/chromium/src/+/40ccb2581137efc2fc7d2a1041073fa00caed75a and was done on purpose. The enter is mutating the disabled value on the input.
,
Jan 3 2018
Thanks for the quick response. I'll look into this change and see if there's a way to work around it in React.
,
Jan 4 2018
Able to reproduce the issue on reported chrome version 63.0.3239.108 and on the latest canary 65.0.3309.0 Using Windows 10, Ubuntu 14.04 and Mac 10.13.1. As the issue is seen from M50(50.0.2634.0) considering it as non-regression and marking it as Untriaged. Note: In M50(50.0.2634.0) both "Blur counter" and "Native Blur counter" are triggered where in reported and latest canary only "Native Blur counter" is being triggered. Attaching the screenshots for reference. Thanks!
,
Jan 11 2018
Yes, the behavior change was intentional, and match to the HTML standard. |
||||
►
Sign in to add a comment |
||||
Comment 1 by krajshree@chromium.org
, Jan 3 2018