-
Notifications
You must be signed in to change notification settings - Fork 91
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
Context menu doesn't work in Chrome #158
Comments
I wonder if Google have changed the tab port API? |
Well I can re-create the problem on Linux with Chrome 72 so I suspect this is a change to the API. Looks like this was last touched in bug #85 but I'll have to do some digging. If you feel upto it you are welcome to have a look yourself. |
I think Google made this change just to prevent |
OK this is weird - it works on my desktop machine... |
sigh Works with Chromium Version 72.0.3626.121 (Developer Build) (64-bit) |
@twlz0ne ok I think I've removed the need for tab_port.sender. Can you test the latest master and I'll make a release. |
Hmm I'm confused as to what is going wrong then.... and chance you could enable the logging messages and capture them for the whole edit sequence? |
There is nothing happened when I click the context menu item
Edit with Emacs
in Chrome.After debugging the source code, I found that the
tab_port.sender
is read-only:The text was updated successfully, but these errors were encountered: