My version of google chrome is 83.0.4103.116 (Build oficial) (64 bits) (cohort: Stable)
But audits tab does not show on devtools.
Any idea of how enable audit tab?
The Audits tab does not exist anymore, it has been replaced with Lighthouse (See What's new in DevTools (Chrome 83)).
Just use Lighthouse.
the Audits panel is now the Lighthouse panel.
Related
I installed Vue.js devtools in my Google Chrome 96 :
https://prnt.sc/2154uz3
But opening laravel 8/vuejs3 app I do not see vue tab in console of my browser : https://prnt.sc/2155psy
What is wrong and how can it be fixed?
Thanks in advance!
The Vue.js shows a tab in dev tools.
Be aware, this will not show if your application is running in production.
NB! You can try this for production mode, it will try build up the same data:
https://chrome.google.com/webstore/detail/vue-force-dev/oohfffedbkbjnbpbbedapppafmlnccmb
My version of google chrome is 83.0.4103.116 (Build oficial) (64 bits) (cohort: Stable)
But audits tab does not show on devtools.
Any idea of how enable audit tab?
The Audits tab does not exist anymore, it has been replaced with Lighthouse (See What's new in DevTools (Chrome 83)).
Just use Lighthouse.
the Audits panel is now the Lighthouse panel.
I'm trying to open Inspect WebView in chrome DevTools, i can see my device and the opened WebView, but when i click on the inspect link, the DevTools window opens for a brief moment and autoclose immediately.
Chrome version is 48.0.2564.116 (64-bit)
Issue was resolved by upgrading to Version 49.0.2623.110 (64-bit)
chrome://inspect/#devices opens a devtools window, but about the time it finishes drawing itself, it closes. No error messages
I'm trying to debug a website, not a native app. Any ideas why it would open and tease me, then close when the mouse gets near the window?
Linux: Version 40.0.2214.111 (64-bit) OS:14.04 Ubuntu
Android: Version 40.0.2214.109 OS: 4.1.2
More interesting details. It works on other tabs, and if I use one of those tabs that is working, and paste in my URL, it closes the devtools
As stated in the docs, your desktop Chrome must be newer than your Android Chrome:
Note: Remote debugging requires your version of desktop Chrome to be newer than the version of Chrome for Android on your device. For best results, use Chrome Canary (Mac/Windows) or the Chrome Dev channel release (Linux) on desktop.
For instance, you might install Chrome Canary/unstable or Chrome Beta on your computer. By using it instead, my inspector started working as expected. Currently, my Chrome Beta is v50 and the Android Chrome, v49.
Couple days ago Google Chrome automatically updated from version 31.* to version 32.0.1700.76 m. After that happened it does not show in DevTools network traffic request/responses of "application/msbin1" type anymore. These requests are visible in all other browsers' dev tools (FireFox, IE) and in Fiddler, but not in Chrome. Also Chrome's popup menu in this version is very glitchy.
I don't see the way to downgrade Chrome to previous version. Please help I don't want to uninstall Chrome.
Network traffic does not even show resources (XAP file) a page loads.
Example:
http://www.microsoft.com/silverlight/pixel-shader/demo/
This page loads file SilverlightShaderApp.xap, however dev tools of new Chrome's version never shows it in network tab.
I posted the question here, because it's developers question, not just chrome users.
I reported this issue on google chrome forum as well: here.
Possibly related bugs:
Issue 173844: Developer tools (Network section) don't show response of requests from flash applications
Issue 335502: XMLHttpRequests from Silverlight is not visible in devtools network tab
To avoid the bug, you could downgrade to Chrome 31. A fully offline installer can be downloaded from http://download.oldapps.com/Chrome/31.0.1650.39_chrome_installer.exe.
If you downgrade Chrome, don't forget to disable auto-update. Also, "star" the relevant issues on Chromium's issue tracker so you'll receive email notifications for progress updates. When the issue is fixed, enable auto-update again.
Often, starting a new version of Chrome renders a profile unusable for older Chrome versions ("Your profile can not be used because it is from a newer version of Google Chrome."). When you see such message on start-up, either delete your old profile (don't forget to make a back-up!) (you can also try to delete some files, according to various users, deleting "Web Data" and "Web Data-journal" is sufficient), or launch Chrome with a new profile directory (--user-data-dir=path\to\profile-dir).
For more information on user profiles, see http://www.chromium.org/user-experience/user-data-directory.