devtools
devtools copied to clipboard
vuejs
Vue tab doesn't show in Chrome DevTools
Version
5.1.1
Browser and OS info
Chrome 77 / Windows 10 1903
Steps to reproduce
I'm not completely sure, but I had all Chrome DevTools settings set to default (fresh Chrome install)
What is expected?
I'm able to use Vue DevTools if it's detected by the plugin
What is actually happening?
I can't access Vue tab as it's not visible in DevTools
I've switched to Appearance > Theme setting from 'System preference' to 'Light theme' and it fixed itself. I've tried switching to 'System preference' and reopening browser and it's still working.
me too ,when i clicked the icon told me 'Vue.js is detected on this page. Open DevTools and look for the Vue panel.' but can't find the panel 点击地址栏旁的图标提醒我'Vue.js is detected on this page. Open DevTools and look for the Vue panel.' 但是并不能找到这个 vue 的panel
Same here. I got it to appear by tweaking the settings in the extensions management, but then it just loaded the Vue logo and nothing else. I got it back working by uninstalling and re-installing. HTH.
I had the issue and noticed that at the extension details/settling page, for google chrome, under "Inspect views" shown the hyperlink "background page (inactive)". Upon clicking it, it open console panel in a new window and the Vue devtools is showing afterward. The hyperlink changed to "background page"
@WeichenTeo, that worked for me. It wouldn't display and the extension showed "background page (inactive)". I clicked it and afterwards the next time I opened the inspector the Vue tab appeared.
You mocking me or us? Don't think we installed the plugin correctly before?
Your unrespectful and aggressive comments don't belong here. Don't expect me to help you further.
Seriously, it really pisses me off when people point to the obvious step most every one of us already did. Every single one of us who had the plugin working before have for one reason or another lost the ability to use it, which is how we ended up here.
Unfortunately not everybody read the docs before opening issues or commenting.
Also, why is local file access needed when the URL is http://localhost/. This makes no sense to me.
If that's really what fixed your issue, I guess you should open an issue in the Chrome tracker.
Wouldn't have thought this PR would still be active, and moreover, get this heated. 😅
I am using localhost, so I didn't think file access would be very relevant.
The bug still occasionally happens, but I just got so used to switching the theme to fix it, that I don't even think about it anymore, so it's a bit hard to estimate how often. Probably less since I started using v6.
I'll try to enable file access and see if there is any difference.
It didn't work for me before. It's a bit related to the Chrome version. I installed it in Firefox and it worked normally. Later, I upgraded the Chrome version, and then it also displayed normally
