User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 Build ID: 20170125094131 Steps to reproduce: Alt S to open internal notes in Spectrum - Dexter & Chaney work application. This also opened the shortcut for History in Firefox at the same time. Actual results: The History window opened at the same time as the Internal Note in Spectrum. Expected results: The past 3 years only the Internal Note would have opened. Not the History Window. I do not want the History Window to open.

Is there a public demo of Spectrum where the issue could be reproduced? It would help to debug and fix the issue. If not, is it possible to provide a demo, even with limited rights on a testing server? (credentials can be send by email)

Not capable of providing a demo. If I could find another program site online that offered shortcuts using the ALT keys, I would check to see if it has the same issue.

Ok, we can try something else. 1) Do you have multiprocess (e10s) enabled in FF51? (type about:support in the location bar and check the line "Multiprocess Windows") If yes, try with e10s disabled: https://wiki.mozilla.org/Electrolysis#Firefox_Release (restart to apply) 2) If that doesn't change anything, you can narrow down a regression range in Firefox as you're able to reproduce the issue. For that, you need to download the tool mozregression and run it. See http://mozilla.github.io/mozregression/ for details and FAQ. If FF50 is fine, run the command "mozregression --good=50" then copy here the final pushlog. Ask me if you need help with mozregression.

okay so with some poking around i found a few things. The site you are using is probably using the keydown method. I found https://codepen.io/anon/pen/PKQqJM which if you click into the bottom area and hit ctl+s it picks up the event and also grabs the event to open tool bar for history. Now also if you click into the upper area and hit the same key combo it will save the pin but it wont open the bar. right now i have the same instance occurring on nightly 57.0a1 and 52.0.2esr, if you could please take a look and tell me if that's the issue you are dealing with and ill take a further look into it at that point and build a test case.