Revert of Don't reset the omnibox state on command-return.

Revert of Don't reset the omnibox state on command-return. (patchset #1 id:1 of https://codereview.chromium.org/2904243002/ )

Reason for revert:
This change caused a new issue: https://crbug.com/743288. While we decide how to proceed, it would be better to revert to the previous behavior.

Original issue's description:
> Don't reset the omnibox state on command-return.
> 
> This was originally added in https://codereview.chromium.org/260008/,
> motivated it appears by a desire to match Safari's behavior. Safari no
> longer does this (the address field state is preserved on command-return
> as the new tab is openeed in the background).
> 
> This change makes Chrome's behavior consistent with Safari, simplifies
> the code, fixes a bug, and is more useful IMO. If you want to open
> several tabs with variations on some search, for example, you can press
> command-return after each, then keep typing to produce the next.
> 
> See discussion in the bug for more info.
> 
> BUG=513966
> 
> Review-Url: https://codereview.chromium.org/2904243002
> Cr-Commit-Position: refs/heads/master@{#475542}
> Committed: https://chromium.googlesource.com/chromium/src/+/1f35c3ffdebd60917647555ac6ec572098967035

TBR=rohitrao@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=513966
Review-Url: https://codereview.chromium.org/2983193002
Cr-Commit-Position: refs/heads/master@{#488362}
Committed: https://chromium.googlesource.com/chromium/src/+/01be2f3a17b5b274392a86dcfe9674af19b83564

[Justin Donnelly, 2017-07-20 19:19:20]

The CQ bit was checked by jdonnelly@chromium.org

[Justin Donnelly, 2017-07-20 19:19:21]

Created Revert of Don't reset the omnibox state on command-return.

[commit-bot: I haz the power, 2017-07-20 19:19:46]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-07-20 19:47:24]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1500578360877650, "parent_rev":
"5e14754953e5bcad7d6f97be05e4c171142e3153", "commit_rev":
"01be2f3a17b5b274392a86dcfe9674af19b83564"}

[commit-bot: I haz the power, 2017-07-20 19:47:41]

Description was changed from

==========
Revert of Don't reset the omnibox state on command-return. (patchset #1 id:1 of
https://codereview.chromium.org/2904243002/ )

Reason for revert:
This change caused a new issue: https://crbug.com/743288. While we decide how to
proceed, it would be better to revert to the previous behavior.

Original issue's description:
> Don't reset the omnibox state on command-return.
> 
> This was originally added in https://codereview.chromium.org/260008/,
> motivated it appears by a desire to match Safari's behavior. Safari no
> longer does this (the address field state is preserved on command-return
> as the new tab is openeed in the background).
> 
> This change makes Chrome's behavior consistent with Safari, simplifies
> the code, fixes a bug, and is more useful IMO. If you want to open
> several tabs with variations on some search, for example, you can press
> command-return after each, then keep typing to produce the next.
> 
> See discussion in the bug for more info.
> 
> BUG=513966
> 
> Review-Url: https://codereview.chromium.org/2904243002
> Cr-Commit-Position: refs/heads/master@{#475542}
> Committed:
https://chromium.googlesource.com/chromium/src/+/1f35c3ffdebd60917647555ac6ec...

TBR=rohitrao@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=513966
==========

to

==========
Revert of Don't reset the omnibox state on command-return. (patchset #1 id:1 of
https://codereview.chromium.org/2904243002/ )

Reason for revert:
This change caused a new issue: https://crbug.com/743288. While we decide how to
proceed, it would be better to revert to the previous behavior.

Original issue's description:
> Don't reset the omnibox state on command-return.
> 
> This was originally added in https://codereview.chromium.org/260008/,
> motivated it appears by a desire to match Safari's behavior. Safari no
> longer does this (the address field state is preserved on command-return
> as the new tab is openeed in the background).
> 
> This change makes Chrome's behavior consistent with Safari, simplifies
> the code, fixes a bug, and is more useful IMO. If you want to open
> several tabs with variations on some search, for example, you can press
> command-return after each, then keep typing to produce the next.
> 
> See discussion in the bug for more info.
> 
> BUG=513966
> 
> Review-Url: https://codereview.chromium.org/2904243002
> Cr-Commit-Position: refs/heads/master@{#475542}
> Committed:
https://chromium.googlesource.com/chromium/src/+/1f35c3ffdebd60917647555ac6ec...

TBR=rohitrao@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=513966

Review-Url: https://codereview.chromium.org/2983193002
Cr-Commit-Position: refs/heads/master@{#488362}
Committed:
https://chromium.googlesource.com/chromium/src/+/01be2f3a17b5b274392a86dcfe96...
==========

[commit-bot: I haz the power, 2017-07-20 19:47:44]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/01be2f3a17b5b274392a86dcfe96...