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

Not working in Inbox #327

Open
selrond opened this issue Jan 25, 2016 · 9 comments
Open

Not working in Inbox #327

selrond opened this issue Jan 25, 2016 · 9 comments

Comments

@selrond
Copy link

selrond commented Jan 25, 2016

Markdown-marked-up text does not react to context menu toggle, nor keyboard shortcut... Same for quick compose, as well as in reply mode...

@tatianagrange
Copy link

It is the same for me. In quick answer and in reply mode.

@brendanmatkin
Copy link

Can confirm this.. using chrome 53.0.2785.143 on OS X 10.11.6

@alexozer
Copy link

alexozer commented Nov 8, 2017

Isn't working for me either. I sometimes get a popup asking to confirm unrendering the changes, which produces glitchy behavior.

@fredley
Copy link

fredley commented Nov 8, 2017

Having installed on Chrome, the help page popped open half way through writing an email (a good 100+ chars in, at least 20 seconds after starting typing). There is no M button on the toolbar, keyboard shortcuts and context menu do nothing.

@timvdalen
Copy link

Came here from the HN thread. The extension works fine for me in Inbox.

screenshot 2017-11-08 at 14 18 55

@alexozer
Copy link

Tried this again, seemed to realize the paradigm is "edit in plain-text, convert, unconvert if need more edits". Actually seems to work fine now for me!

@tomasz-wiszkowski
Copy link

I don't think this is about the paradigm. In fact, I'm suffering from that same problem as OP.

I have the markdown toggle button enabled, but it doesn't do anything.
Keyboard shortcuts don't work.

I can open markdown options page and successfully use my shortcut (or button) to toggle between rendered and plain text modes. Inbox and gmail don't work for me at all.

It used to work just a few months ago; I used it in December if i'm not mistaken and it worked. Right now it no longer does anything

@ChuliangXiao
Copy link

It didn't work for me at first.
After I closed and relaunched Chrome, it worked.

@lrdegeest
Copy link

Just tried this extension on Chrome. Does not work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants