Infinite Loop with OnBlur Event
Reported by
harada.e...@gmail.com,
Mar 13 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Steps to reproduce the problem: First Way (https://jsfiddle.net/3L1q372b/): 1. Focus the first and press TAB Key. 2. Now you have an infinite loop of alert message. Second Way(https://jsfiddle.net/3L1q372b/): 1. Focus First Input. 2. Click where you write the URL. 3. Press ALT+Enter to access the URL in another tab. 4. Now you have an infinite loop of alert message. What is the expected behavior? Just show alert message one time. What went wrong? It creates a infinite loop with alert message. Did this work before? No Chrome version: 56.0.2924.87 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version:
,
Mar 14 2017
Able to reproduce the issue on windows 7, Ubuntu 14.04 and Mac 10.12.3 using chrome version 56.0.2924.87 and canary 59.0.3040.0. This is regression issue in M54.Please find the bisect informstion as below Narrow Bisect:: Good::54.0.2832.0 -- (build revision 412743) Bad: 54.0.2833.0 -- (build revision 413134) Change Log:: https://chromium.googlesource.com/chromium/src/+log/e339d7ccee8a30818ed8d7c511ca0df01b8342c3..cbaec91aacdd72f3f2941ff3f7b7706100d5081e Unable to find the exact suspect from the CL. Could any one from dev team please look into this issue. Thanks,
,
Mar 15 2017
Remove Blink>DOM>Events
,
Mar 23 2017
We are having the same issue with onBlur validation in our commercial application. Windows 7,8,10 There appears to be a difference: Chrome version 57.0.2987.98 - goes into a dead loop immediately on any Blur Chrome version 57.0.2987.110 - goes into a dead loop after clicking outside Chrome. Since we have onBlur validation all over the place (136 forms and pages) we will be advising customers to stop using Chrome until this is resolved.
,
Mar 24 2017
,
Mar 24 2017
This is the same as issue 666205 . Unfortunately, the issue is "working as intended", so there is no fix as of now. In summary, the second blur event is sent because the alert popup window gained focus, but sent to the <input> *after* the popup is closed, because during the alert popup is open, event loop is suspended and the event delivery is delayed until the event loop resumes.
,
Sep 29 2017
,
Sep 29 2017
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by nyerramilli@chromium.org
, Mar 14 2017