Pressing "ENTER" on blue buttons doesn't submit a form anymore


Observed Behavior:

The focused button (e.g. blue buttons) doesn’t submit form on ENTER press in Google Chrome 73.0.3683.86 (Mac). It was working correctly in previous Google Chrome versions.

Also working correctly on Firefox 66.0.2 (Mac).

Expected Behavior:
Form is submitted as if I’ve clicked on the blue button with a mouse/trackpad.

Phabricator Version:

Reproduction Steps:

  1. go to a commit page (e.g.
  2. select code to add inline comment
  3. type in comment text
  4. press TAB key until you see blue “Save Draft” button is focused
  5. hit ENTER

Attempt to add commit-wide comment would also fail (button is focused, but pressing ENTER does nothing).

Basically before pressing enter on any control except textboxes (e.g. a dropdown) caused form to be submitted. Now it doesn’t.

Thank you.



This sounds a lot like a bug in Chrome. Have you reported it to Chrome?



I’ve created an example to demonstrate submit on ENTER here:,output

Just in case I’m pasting it’s HTML also here:

<!DOCTYPE html>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width">
  <title>JS Bin</title>
	<style type="text/css">
		input:focus {
			border: 1px solid red;
			font-weight: bold;

	<form method="post">
		Field 1: <select name="form_input1">
			<option value="1">Option 1</option>
			<option value="2">Option 2</option>
		Field 2: <input type="text" name="form_input2"/><br/>
		Field 3: <input type="text" name="form_input3"/><br/>
		<input type="submit" value="Submit button"/>

As you can see from above example submit on ENTER works perfectly on any of the fields.

Phabricator might be doing some special keypress handling (e.g. because forms are pretty complex), not a regular form submit that no longer works in Google Chrome, but still works in Firefox.

Update (I wasn’t able to add new comment on closed topic):

The problem was caused by “Evernote Web Clipper” Google Chrome extension, that with “Shortcuts” enabled was catching them (likely event propogation was disabled in the process) and therefore website itself wasn’t able to detect keypress.



Nope I haven’t.


closed #5