Chrome Version: <From about:version: Google  57.0.2987.98 (64-bit)>
Chrome OS Version: <From about:version: Platform x.x.x.x>
Chrome OS Platform: <Macbook pro (retina, 15 inch, 2.2 gh, core i7, 16 gb, single iris pro 1538 graphics card)S>
Network info: <cable vison, encription mot known n600 netgear 3400 version cablevision (propbably v1>

Please specify Cr-* of the system to which this bug/feature applies (add
the label below). This question O don't inderstand fully, although the feature effected is keyboard input (is this a basic requirement or a feature, it would be if another form of input was considered to be the default input.; on certain times it is not possible to produce heyboard inputs without the sound prompt that suggests that an input is not--possible, though it a keyboard input is not possible.

Steps To Reproduce:
Introduction - this problem only works with google search
limitation of claim, I have only attempted this with google, yahoo, and Bing
Further limitation of the three, yahoo does not have, in its default mode, an in screen search input.
Issue
This effects text or numerical input carried out through the means of the notebook's keyboard; I have not attempted this with an external keyboard.
This fault is precipitated by after the creation of a new tab or window, but only though use of the keyboard, and not with the use of the menu command, either Menu/File/New Tab or Menu/File/New Window
This fault only affects the in window text box; care has to be made to preselect the input box or the search box in the URL screen will be selected

Number one version with tabs or with windows
(1) Create new tab, or window with keyboard command; COMMAND N, or COMMAND T
(2)Attempt to enter text, meaning letters, numbers in the in screen input box
first result
No text will be entered, and if the system sounds are enabled a beep indicating that input is not possible. 
(3) create new window or tab, as above.
(4) Return to previously created tab or window
second result, input will work as expected.


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

What is the impact to the user, and is there a workaround? If so, what is
it?
Some frustration; I hear that sound again, but I can use the url input or the strange work around above 

Please provide any additional information below. Attach a screen shot or
log if possible. I have provided a report from sysdiagnose

Last Guess, in MacOS, as previously the keyboard (not unexpectedly is a kernal controlled event, but the menus are governed by APPKIT, but why this only effects google search. Does chrome attempt to control keyboard interactions directly through APPKIT, but then that sounds normal, who would want to mess with the kernal for simple keyboard inputs


 

Deleted: Google Chrome Helper_2017-03-11-140508_billyowls-MacBook-Pro.wakeups_resource.diag 112 KB

Google Chrome Helper_2017-03-11-140508_billyowls-MacBook-Pro.wakeups_resource.diag 112 KB Download

Deleted: Google Chrome Helper_2017-03-12-102647_billyowls-MacBook-Pro.wakeups_resource.diag 149 KB

Google Chrome Helper_2017-03-12-102647_billyowls-MacBook-Pro.wakeups_resource.diag 149 KB Download