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

Ctrl+M doesn't work from markdown Preview window #12939

Closed
mousetraps opened this issue Sep 28, 2016 · 4 comments
Closed

Ctrl+M doesn't work from markdown Preview window #12939

mousetraps opened this issue Sep 28, 2016 · 4 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug *out-of-scope Posted issue is not in scope of VS Code webview Webview issues

Comments

@mousetraps
Copy link
Contributor

mousetraps commented Sep 28, 2016

Testing #12519

Ctrl+M to toggle "Tab moves focus" mode does not work from File Preview window from markdown file - see below - while preview of blah.md is open, Ctrl+M does nothing
image

@jrieken jrieken removed their assignment Sep 29, 2016
@jrieken
Copy link
Member

jrieken commented Sep 29, 2016

It should not do anything as the tab moves focus is for the editor in which tab usually does something else. For me the bug here is that the status bar still shows the tab-moves label even though no code editor is showing

@mjbvz mjbvz added the markdown Markdown support issues label Oct 4, 2016
@alexdima alexdima added the bug Issue identified by VS Code Team member as probable bug label Oct 6, 2016
@alexdima
Copy link
Member

alexdima commented Mar 2, 2017

@jrieken "Tab moves focus" is no longer an editor instance specific thing. It is a big fat static that toggles it for all editors. I think the keybinding doesn't reach us as a limitation of the webview.

@alexdima alexdima assigned jrieken and unassigned alexdima Mar 2, 2017
@jrieken jrieken added webview Webview issues and removed markdown Markdown support issues labels Mar 2, 2017
@jrieken
Copy link
Member

jrieken commented Apr 13, 2017

@alexandrudima It actually does reach us but should I then manually focus the next thing? Today it focuses things like links and elements of the webview...

@jrieken jrieken assigned mjbvz and unassigned jrieken Sep 6, 2017
@mjbvz mjbvz added the *out-of-scope Posted issue is not in scope of VS Code label Sep 18, 2018
@vscodebot
Copy link

vscodebot bot commented Sep 18, 2018

This iteration we focus on issue grooming. This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

@vscodebot vscodebot bot closed this as completed Sep 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug *out-of-scope Posted issue is not in scope of VS Code webview Webview issues
Projects
None yet
Development

No branches or pull requests

4 participants