on 51 chrome browser all PC has no problem

 Issue 703406  has been merged into this issue.

This will be a duplicate of  issue 666205 

but sending it to the Blink>Focus to triage it. Perhaps it is something that they can think about fixing since other vendors behave differently.

Hmm, interesting, I tested this on Windows 10 Pro 64bit + 59.0.3046.0 (Official Build)
canary, and the infinite loop reproduced.  To make the thing worse, the alert dialog
didn't have "no more dialog on this page" checkbox.  But the repro html really
looks like what  issue 666205  was about - let me check this again.

Able to reproduce this issue on Windows, Mac and Linux on Latest Stable# 57.0.2987.123.
Below is the behavior of the issue in different builds --

Observation (i)
Till M53 builds the behavior is as below:
Focusing on input and clicking outside the text input, pop-up opens.
Click ok and again click outside text input, pop-up opens
Note: "Prevent this page from creating additional dialog with OK label. Once OK is clicked no pop-up is seen.

Observation (ii)
From M53 to M59 builds including Chrome Beta# 58.0.3029.33 and Latest Dev# 59.0.3047.0 / 59.0.3047.4 the behavior is as below:
Focusing on input and clicking outside the text input, pop-up opens.
Click OK and observe the pop-up keeps on coming.
Note: "Prevent this page from creating additional dialog with OK label. Once OK is clicked no pop-up is seen.

Observation (iii)
In Chrome Canary# 59.0.3053.0 the behavior is as below:
Focusing on input and clicking outside the text input, pop-up opens.
Click OK and observe the pop-up keeps on coming.
Note: "Prevent this page from creating additional dialog with OK label is not seen. The windows has to be closed to exit the pop-up.

Please let me know if any more information is required.
Thank You.

Thanks msrchandra for the data points.

So 59.0.3053.0 is the only version that "Prevent this page from creating additional
dialog" isn't seen, and this regressed(?) between 59.0.3047.0 and 59.0.3053.0?

If so, could you bisect to identify which caused the change?

Able to reproduce this issue on Windows 10, Ubuntu 14.04 and Mac 10.12.5 with chrome Beta #60.0.3112.66, Dev #61.0.3153.4, Canary #61.0.3159.0 but not on Stable #59.0.3071.115, 

Good Behavior :
================
1. Focusing on input and clicking outside the text input, pop-up opens.
2. Click OK and observe the pop-up keeps on coming.
   Note: "Check the "Prevent this page from creating additional dialog" with OK label. Once OK is clicked no pop-up is seen.


Bisect Info:
===========
Good build : 60.0.3087.0,  Revision Range -468507
Bad build  : 60.0.3090.0,  Revision Range -469538

Unable to provide per-revision bisect result, since builds are not invoking 

The following CL's between good and bad build versions
===========================================
https://chromium.googlesource.com/chromium/src/+log/60.0.3087.0..60.0.3090.0?pretty=fuller&n=10000

The suspecting CL is :
-----------
Review-Url: https://codereview.chromium.org/2860093002

kochi@- Could you please look into this issue, if it's related to your change?  if not could you please help us to reassign this issue to the right owner.

 Issue 746755  has been merged into this issue.

avi@, do you have any idea "Prevent this page from creating additional dialog"
checkbox is not working?

That checkbox was removed with the new version of the javascript dialogs.

Isn't this bug about the focus event?

Yes, about focus event, but that the checkbox has gone means that there is
no escape hatch for the infinite loop (maybe ctrl-W, though).

Yes. The intended escape hatch for infinite dialogs is closing the tab.

Let me close this by merging to 666205, which discusses the same issue,
as the current behavior is just what is expected - including "Prevent
this page from creating additional dialog" is no longer available.

Once the infinite loop happens, closing the tab is the only way to
get out of it (thus you lose the data on that page, etc. etc.).

I noticed that the last two infinite loop reported problems had their status set to closed and merged them into an issue that has a status of WontFix. 

If a form is using the onblur event, followed by an alert message, and then a focus() JavaScript call back to the form field, the current implementation of the chrome browser causes an infinite loop to occur. 

This type of form field validation would be used in many different places. Even if this isn't a preferred method of validating a particular form field, that isn't the issue. The issue here that could break a lot of existing form fields is that the expected behavior of the browser in this case is not correct.

Does assigning these reported problems to an issue that has a status of WontFix mean you have no intention of fixing this error that causes the User's browser to lock up? 

If it isn't fixed, developers would need to check all of their onblur events to make sure they don't use an alert message followed by a focus() JavaScript call back to the form field and remove/modify that code to prevent something like that happening to their Users. Or they would have to change the onblur to onchange, but then what if changes are subsequently made that breaks the onchange expected behavior?

Thank you for addressing this.