I was speaking with Gijs about this. It may be due to the fact openLinkIn focuses the content window before the load https://searchfox.org/mozilla-central/rev/bc3600def806859c31b2c7ac06e3d69271052a89/browser/base/content/utilityOverlay.js#548 then the content window ends up getting the keyup event of the last typed letter. I was expecting us to not send a chrome generated event down to content like that, but we don't seem to be checking them? Olli, is this something frontend should handle, or should it be handled at the event handling level?
Bug 1641287 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This also reproduces using the Search Bar. I was speaking with Gijs about this. It may be due to the fact openLinkIn focuses the content window before the load https://searchfox.org/mozilla-central/rev/bc3600def806859c31b2c7ac06e3d69271052a89/browser/base/content/utilityOverlay.js#548 then the content window ends up getting the keyup event of the last typed letter. I was expecting us to not send a chrome generated event down to content like that, but we don't seem to be checking them? Olli, is this something frontend should handle, or should it be handled at the event handling level?
This also reproduces using the Search Bar. And I can imagine it would be for any input field that ends up calling into openLinkIn. I was speaking with Gijs about this. It may be due to the fact openLinkIn focuses the content window before the load https://searchfox.org/mozilla-central/rev/bc3600def806859c31b2c7ac06e3d69271052a89/browser/base/content/utilityOverlay.js#548 then the content window ends up getting the keyup event of the last typed letter. I was expecting us to not send a chrome generated event down to content like that, but we don't seem to be checking them? Olli, is this something frontend should handle, or should it be handled at the event handling level?