Using this cheat sheet of "constants", I reassigned the keyboard code for opening the side menu. It was triggered by F1 (coded as 112) in the script. Since Chrome & Safari are not complying with that coding system, I switched the trigger to the escape key (coded as 27)
If you are running chrome, try pressing Shift+Escape to open the menu. Safari uses the shift key in conjunction with it, so I'm assuming Chrome will be the same. In Firefox you just have to press escape and the script will open the menu. I struggled to find a key that would be good to use. Escape wasn't my favorite choice, but it was the one I felt was least likely to conflict between programs.
Using this cheat sheet of "constants", I reassigned the keyboard code for opening the side menu. It was triggered by F1 (coded as 112) in the script. Since Chrome & Safari are not complying with that coding system, I switched the trigger to the escape key (coded as 27)
If you are running chrome, try pressing Shift+Escape to open the menu. Safari uses the shift key in conjunction with it, so I'm assuming Chrome will be the same. In Firefox you just have to press escape and the script will open the menu. I struggled to find a key that would be good to use. Escape wasn't my favorite choice, but it was the one I felt was least likely to conflict between programs.
Since I can't write javascript, it took me a while to decipher what was causing the defect. Google must be based on the same code used to write Safari. I guess they want to create new "constants" so that it looks like IE is misbehaving.