User Agent: Mozilla/5.0 (Windows NT 6.1; rv:36.0) Gecko/20100101 Firefox/36.0 SeaMonkey/2.33.1 Build ID: 20150321194901 Steps to reproduce: open https://github.com/mendhak/gpslogger press / to start 'find as you type' if auto find is not enabled type 'bus' Actual results: seamonkey finds the first two characters but as soon as 's' is pressed the search field at the top of the screen gets focused, find as you type is interrupted and any additional characters will be typed into the search field on the page instead of find as you type string. Any 's' in the input string breaks find as you type. Expected results: find as you type should've continued uninterrupted regardless of what characters are typed
"Using keyboard shortcuts" https://help.github.com/articles/using-keyboard-shortcuts/
The problem here is that there are keypress events (with nice char codes) and keydown events (which only have key codes). So we listen out for keypress events, but the page is listening out for keydown events, which means it gets them first.
Created attachment 8603839 [details] [diff] [review] Proposed patch I added a capturing keydown event listener to stop the propagation of keydown events to content while we're finding. I also capture keyup events for good measure, and stop the propagation of keypress events too. (I don't bother with the initial / or ' since that's a bubbling event in the system group anyway.)