Tested the issue in Android and could not reproduce the issue.

Steps Followed:
1. Launched Chrome .
2. Navigated to https://embed.plnkr.co/ReNeRbPX0lFFRr8SQGkM/
3. Focused the first form field in the second form
4. Pressed "Enter" on phone's keyboard.
5. Observed focus on the same text field and keydown event triggered

Chrome versions tested:
63.0.3239.111

OS
Android 7.0.0, 6.0.1, 5.0.0

Android Devices
S7, S5, Micromax

@caseyh: Could you please attach a screencast for further triage.

Thanks!!

Sandeep,

Thanks for checking into this. I took a screencast which you can view here: https://streamable.com/m7ezk.

-Casey

Thank you for providing more feedback. Adding requester "sandeepkumars@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

I was able to test on my friend's phone and was able to recreate this issue. That was on a Samsung Galaxy S7 running Android 7.0.0, Chrome 63.0.3239.111. 

Steps:

1. Select "Input 2"
2. Press "Enter"
3. Alert does not pop up. Focus moves to "Input 3."

Tested the issue in Android and able to reproduce the issue. 

Steps Followed:
1. Launched the Chrome 
2. Navigated to https://embed.plnkr.co/ReNeRbPX0lFFRr8SQGkM/
3. Focus the first form field in the second form.
4. Pressed "Enter" on phone's keyboard
5. Observed focus is moving to next field

Chrome versions tested:
63.0.3239.111(Stable)

OS:
Android 6.0.1

Android Devices:
Samsung S7

Using the per-revision bisect providing the bisect results,
Good build: 62.0.3179.2
Bad build: 62.0.3180.0

You are looking for a change made after 492587(GOOD), but before 492588(BAD).

CHANGELOG URL:
The script might not always return single CL as suspect as some perf builds might get missing due to failure.

https://chromium.googlesource.com/chromium/src/+/041c0b075176fb9bca94fd67fc1b6053a4df2e1c

From the CL's above, assigning the issue to the owner concerned.

@Ajith: Could you please look into the issue, and assign it to concerned owner if this is not related your change.

Please navigate to below link for log's and video--
go/chrome-androidlogs/804622

Note: This issue is not observed in Desktop.

Thanks!

Looping to few of the reviewers.

If possible can we target a fix for M66 or M65. Adding RBS fort M66, feel free to modify if needed.

This is an intended behavior change. Also, in  issue 790790  we decided to keep the current behavior.

On Android, IMEs never send 'enter' key event except on a physical keyboard. We decided not to translate 'focus change' request to key events because there are other ways to move focus such as touch events and mouse events.

Also, per  http://crbug.com/790790#c18  this does not work on Safari on iOS, either.

For what it's worth, I came across this bug when attempting to implement the Angular Material Chips component in my web app. Chips are added by pressing "Enter." With this change in Chrome for Android, it's not actually possible to add a chip in a form with multiple fields (see https://github.com/angular/material/issues/11081). This is an unexpected behavior change. To have no way to detect certain keyboard events (when it was previously possible) is very frustrating as a developer.