-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Opéra browser and SEChatModifications #55
Comments
Related [I guess]: You can't go down when in selection mode (neither with CTRL+down or just down) |
Opera was throwing additional events related to the CTRL and arrow keys that weren't being taken into consideration by the keyboard navigation handlers. I've updated the script to consider these cases and handle them appropriately. |
There is still one problem, when you can edit your previous messages, you can't make a new reply, it always brings up the modification state. |
Gah, you're right. Sorry, I thought I tested that case. I'll fix the problem here shortly. |
Any luck with the problem? |
Yes, actually! I'll have a fix pushed out sometime before Sunday (hopefully sooner, but just in case) |
Its seem that Opéra browser has little trouble to handle the CTRL+UP shortcut to select the lines when you can still edit your previous messages.
It goes through all editable messages like you did not have the userscript and then pops the green selection area. Still if you try to reply to a message, it edits the last message instead.
I guess the CTRL key does not take priority over single up arrow key.
The text was updated successfully, but these errors were encountered: