Similar to  bug 865439 .

Thanks for filing the issue!

@Reporter: Could you please let us know if the issue is with any specific application, and it would be very helpful if given a confirmation, whether this is similar to  bug 865439 . Any further inputs from your end may be helpful. 

Yes, it is very similar to 865439. In my cas the special application used is "KeePass 2" which you can get at https://sourceforge.net/projects/keepass/files/KeePass%202.x/2.40/KeePass-2.40-Setup.exe/download

I'm using hotkey Ctrl-Alt-A for global auto typing.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Tested the issue on chrome reported version# 69.0.3497.81 using Windows-10 with steps mentioned below:
1) Launched chrome reported version and installed "KeePass 2" from URL provided in comment# 5
2) In KeePass added a new entry for FB login page with URL, login ID and password
3) Navigated to FB login URL in New Tab Page in chrome window, clicked on login ID field and pressed "Ctrl+Alt+A", didn't observed any data entered in the fields
Observations: Also tested the issue on chrome version# 68.0.3440.106(as per comment# 0 "Did this work before? Yes 68.x.x.x"), there also seen the same behavior.

@Reporter: Please find the above information and provide your feedback on it which help in further triaging the issue in better way.

Thanks!

Well, I've tested as follows

1) Installed Chrome 68.0.3440.10600 (via chocolatey)
2) Using KeePass 2 v2.39.1, with the following Plugins:
   KeePassHttp 1.8.4.2
   WebAutoType 5.2.2.0
3) Add Entry with URL https://www.facebook.com/
4) Navigate to that site
5) Place cursor in username field
6) Press Ctrl-Alt-A
--> works

Installed newer version of Chrome and done the same
--> does nothing

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Retested the issue on reported chrome version 69.0.3497.81 and on 68.0.3440.106 (...as mentioned in C#8) Couldn't find any difference in the behaviour of both mentioned versions. Hence requesting someone from UI>Input>KeyboardShortcuts team to have a look into this and help in further triaging it.

@Reporter: As mentioned in C#8, version 68.0.3440.106 was working fine...could you please attach a screencast of the same, which helps to triage the issue further in a better way.

Thanks!

Found an issue report on the KeePass plugin vendor's site (https://sourceforge.net/p/webautotype/discussion/general/thread/44fd6879/)
It seems that the cause is slightly different and related to Chromium's accessibility features. The vendor of the WebAutoType plugin filed a bug for this issue https://bugs.chromium.org/p/chromium/issues/detail?id=881753.

When Chromium is started with cmdline arg "--force-renderer-accessibility" the feature works as expected.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

As per comment#11 by reporter it's clear that the cause for this issue is being worked upon in Issue 881753, which was filed by the vendor of the WebAutoType plugin. And it is said that it's working as expected when chrome is started with command line arg "--force-renderer-accessibility", hence removing Needs-Bisect label. Please feel free to add the label back if required.

Thanks!

As per comment# 4, 7 & 10, unable to reproduce the issue from TE end, hence requesting someone form the UI>Input>KeyboardShortcuts team help in providing further inputs on this issue. Adding TE-NeedsTriageHelp label to it.

Thanks!

***Mass UI Triage*** As per comment #14