You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Open the Vue devtools inside the Chrome developer tools.
Next hit cmd P (ctrl P on Windows) in order to open the 'file picker' inside Chrome devtools.
What is expected?
I expect to open the built-in 'file picker' which, inside devtools, also listens to the cmd P command.
On every other pane in the devtools this command works as expected.
What is actually happening?
The 'print page' modal appears. This results in trying to print the current Vue devtools state on an A4 piece of paper.
I use cmd P a lot to jump to files immediately when I see a bug in the state. However, this bug prevents me from doing so from the vue devtools.
Also, Firefox devtools doesn't seem to suffer from the issue, since cmd p is only supported from the debugger panel.
The text was updated successfully, but these errors were encountered:
Version
4.1.4
Browser and OS info
Chrome 66 / MacOS 10.13
Steps to reproduce
Open the Vue devtools inside the Chrome developer tools.
Next hit cmd P (ctrl P on Windows) in order to open the 'file picker' inside Chrome devtools.
What is expected?
I expect to open the built-in 'file picker' which, inside devtools, also listens to the cmd P command.
On every other pane in the devtools this command works as expected.
What is actually happening?
The 'print page' modal appears. This results in trying to print the current Vue devtools state on an A4 piece of paper.
I use cmd P a lot to jump to files immediately when I see a bug in the state. However, this bug prevents me from doing so from the vue devtools.
Also, Firefox devtools doesn't seem to suffer from the issue, since cmd p is only supported from the debugger panel.
The text was updated successfully, but these errors were encountered: