Chrome Version: 663.0.3239.140 (Official Build) (64-bit)
Chrome OS Version: 10032.86.0 (Official Build) stable-channel samus
Chrome OS Platform: Chromebook Pixel 2015 (Google_Samus.6300.174.0)

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).
Cr-UI-Input-Text
Cr-IO-Keyboard

Steps To Reproduce:
(1) Connect an external Apple keyboard to a Chromebook (I used a Bluetooth U.S. Apple Keyboard, the direct predecessor and functionally equivalent to the current "Magic Keyboard - US English").
(2) Make sure the modified key settings at chrome://settings/keyboard-overlay are set to defaults (Search=Search, Ctrl=Ctrl, Alt=Alt, Caps Lock=Caps Lock, Escape=Escape, Backspace=Backspace).
(3) Using the external keyboard, press Command-N

Expected Result:

- A new browser window is opened.

Actual Result:

- Nothing happens

How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?)

- Always

What is the impact to the user, and is there a workaround? If so, what is it?

- This makes difficult for an Apple external keyboard to be used for both a Mac OS and a Chrome OS system, since actions recorded in muscle memory on one system (like Command-N, the only way to get a new Chrome window with a keyboard shortcut on Mac OS) do not work on the other (Chrome OS).
- There is no workaround I'm aware of: Mapping the key named "Search" in chrome://settings/keyboard-overlay to "Ctrl" would make things work for the Apple keyboard but break more important things for the Chromebook's internal keyboard (it breaks the Chromebook's Search key functionality).

Please provide any additional information below. Attach a screen shot or
log if possible.

- There seems to be some confusion about the intended default behavior for the Command key on Apple keyboards:  Issue 434346  (https://bugs.chromium.org/p/chromium/issues/detail?id=434346) suggests the Command key is or should be equivalent to a Chromebook's search key, which presents the user experience issue described here, while  issue 471753  (https://bugs.chromium.org/p/chromium/issues/detail?id=471753),  issue 133896  before it (https://bugs.chromium.org/p/chromium/issues/detail?id=133896), and comment 11 of  issue 434346  (https://bugs.chromium.org/p/chromium/issues/detail?id=434346#c11) all suggest the Apple keyboard's Command key should behave as Ctrl, at least by default, which would solve the issue described here.