Skip to content
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

[Google Chrome] Keyboard shortcut not working on Gmail composer (new conversation) #188

Closed
paulodiovani opened this issue Jun 9, 2014 · 8 comments
Milestone

Comments

@paulodiovani
Copy link

When starting a new conversation on GMail (click on "COMPOSE" button or typing C) the keyboard shortcut set for Markdown Here does not Work.

By clicking on the extension button or using the context menu the extension still converts to/from markdown.
By anwering an existing conversation the keyboard shortcut still works.

Thus bug seens to be present since version 2.11.0.

@manfromanotherland
Copy link

Same here.

OS X 10.9.3
Chrome Version 36.0.1985.49 beta

@mlindegarde
Copy link

I'm experiencing the same problem on multiple computers.

Windows 7
Chrome Version 35.0.1916.114 m

@adam-p
Copy link
Owner

adam-p commented Jun 15, 2014

I have reproduced it as well on Win 8, Chrome 35.0.1916.153 m.

The problem isn't obvious. There's no error output in either the browser console nor the extension background console. I also tried changing the MDH shortcut, but it doesn't seem to make a difference.

It's going to take some digging, but I'll sort it out as soon as I can.

@jordi9
Copy link

jordi9 commented Jun 25, 2014

+1

OS X 10.9.3

@averagewizard
Copy link

Same here.

OS X 10.9.4
Chrome 35.0.1916.153

@mrchief
Copy link

mrchief commented Jul 18, 2014

Glad I'm not the only one... I was even thinking chrome messed it up!

@kcmckell
Copy link

+1
OS X 10.9.3
Chrome 36.0.1985.125

adam-p added a commit that referenced this issue Aug 26, 2014
…ner to grab event in capture phase. It's likely that Google added a capture keydown handler that broke the old handler.
@adam-p
Copy link
Owner

adam-p commented Aug 26, 2014

Fixed in 2b9bae4. Going to use it for a while to make sure it's good and then put out a new release (this weekend at the latest, let's say).

@adam-p adam-p closed this as completed Aug 26, 2014
@adam-p adam-p added this to the Next release milestone Aug 30, 2014
@adam-p adam-p modified the milestones: v2.11.1, Next release Sep 18, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants