I used to be able to hover my mouse over the Name column in the Network tab in the Chrome developer tools, and see a tooltip with the URL of the resource downloaded. That seems to have gone now, so I need to show the URL column which takes up so much space when I don't need it 99% of the time. Is there any way to get the tooltip back?
UPDATE CHROME 102: The network request hover tooltip is back on the Chrome 102 version.
It was removed on the Chrome 99 version. This has been reported and the project member was willing to hear from the users and they made a commit to bring it back, but not sure which upcoming version will have this commit included. As a web developer, I know how important is this small feature.
As of now Chrome 101 didn't have this issue fixed.
Related
Following the instructions in the Chrome blog Prerender pages in Chrome for instant page navigations, I am trying to enable pre-rendering on a website. I have added this snippet just before </body>.
<script type="speculationrules">
{
"prerender": [
{
"source": "list",
"urls": ["/Test/1","/Test/2","/Test/3"]
}
]
}
</script>
However, on the latest version of Chrome 108, none of these valid URLs are prefetched or prerendered when opening the page. I can confirm this in the Network tab of Dev Tools, and by following links to the pages which take the usual load time.
In the console, HTMLScriptElement.supports('speculationrules') returns true.
Am I missing something?
I can confirm this in the Network tab of Dev Tools
As the new prerender happens in a separate process (effectively like a background tab) any network calls are not shown in the current page’s DevTools. The Chrome team are working on adding DevTools support.
So here’s a few things to check:
Chrome doesn’t prerender when it’s already using a lot of memory. Try restarting Chrome with just that tab to rule this out.
Make sure you have “Preload pages” ticked in Settings->Privacy & Security->Cookies and other site data
Chrome Canary has a handy experimental setting which shows the reason pre-renders fail worth checking that out. Hopefully that will make it to stable soon.
It’s worth confirming if this is a specific issue to your site, or a general prerendering issue. Checkout the demo linked from that article and let us know if that works
Switching tabs currently cancels any prerenders. So make sure you launch straight from your page.
URL param differences can prevent prerendering being activated as it’s effectively not the same page.
There have been a few bug fixes since 108, so it maybe you’re hitting one of those? Check Dev, Beta, or Canary versions.
There is a “holdback” group of people we randomly select to disable this feature so we can continue to monitor it as it is rolled out, and compare to those not using it. It could be you’re in this group. Unfortunately there’s no easy way to tell this (the Chrome team is working on adding this). Try guest mode to see if that works which is usually the best sign you’re in this group.
Might be able to advise more after you try above steps and let me know.
In recent versions of Chrome-based browsers, for some reason (probably, not a bug, it's a feature), after debug mode is detached, Chrome leaves this notification:
"Programm started debugging this browser"
Screenshot
Basically, I run this code
let debugee = {tabId: sender.tab.id};
chrome.debugger.attach(debugee, '1.2', ()=>{});
chrome.debugger.detach(debugee);
And see the picture above. Chrome removed this notification on detach until version 80 (or so).
I've found the description of the issue:
https://chromium.googlesource.com/chromium/src/+/HEAD/chrome/app/generated_resources.grd
<!-- DevTools attached infobar -->
<message name="IDS_DEV_TOOLS_INFOBAR_LABEL" desc="Label displayed in an infobar when external debugger is attached to the browser. The label does not disappear until the user dismisses it, even if the debugger is detached, and so should not imply that the debugger must still be debugging the browser, only that it was, and could still be.">
"<ph name="CLIENT_NAME">$1<ex>Extension Foo</ex></ph>" started debugging this browser
</message>
I'm looking for a suggestion on how to clear or disable this message automatically, from the chrome extension.
TL;DR there's no such method.
The new behavior in Chrome is the consequence of an awkward fix for a security problem: a malicious extension can quickly do a lot of damage via chrome.debugger API and no one will know that something even happened if the work was performed in less than say 100ms.
Since a security problem was involved, the old behavior won't be restored, but they agreed the UI should at least reflect the current debugger state, see https://crbug.com/1096262. Their current plan is to auto-close the infobar after being visible for >=5s if the extension has detached and update the buttons/strings to be in sync with state.
A workaround is to run chrome with --silent-debugger-extension-api command line switch. It's a dangerous switch though in the sense that you'll have to be careful not to install a malicious extension that uses debugger permission either right away or upon an update.
I have a screen full of code that displays for about half a second on loading some pages in chrome.
I managed to grab a screenshot of it.
I think this one is from a google search for the London tube map.
I have disabled chrome extensions and antivirus but it still appears.
Does anyone know what this is?
In this particular instance the code is generated by Bitdefender Traffic Light extension. If the antivirus is installed, the extension seems to be enabled without being displayed in Chrome's list of extensions.
Disabling the antivirus doesn't seem to disable the extension. But you can clearly see it is activated in a google search as each link has a specific icon next to it.
Other extensions might do a similar thing, but in the lower-left part of the screenshot, the code is:
fraud_link = "http://trafficlight.bitdefender.com/info?url={URL}&language=en_US";
Which makes it obvious this extention is causing the code to be displayed.
With Chrome 32.0.1700.77 the new emulator tab is handy except it's the default tab when I refresh my page.
During my standard development workflow, I constantly refresh the page when I make changes. I usually have the console window open at the bottom of the network or source views. But every single time I refresh the page, the Emulators tab takes focus and I can't see the console.
This is truly annoying since the app will fail because of a simple JavaScript typo, but I can't see the console without clicking one more time (to focus the console tab).
Has anyone found a workaround for this?
Combined with the Chrome Developer Tools unresponsive since update 32.0.1700.76 m issue, I would have to say Google really tripped up this release.
Unfortunately there doesn't seem to be a workaround yet. It looks like there has been a bug reported to Google as found on this thread, but no fix has come about yet.
I think the only way (right now) to prevent the console tab from being hidden when needed is to avoid using the emulator or revert to a previous version of Chrome.
Hopefully a fix comes soon!
It's been a while since this post was made, but I came across the same issue recently. When you have the developer toolbar open, the phone icon beside the "Elements" tab should be blue. Clicking that will disable Emulation.
source: https://groups.google.com/d/msg/google-chrome-developer-tools/g_93_bKmaiA/SdHk0aXdEo4J
When I open a separate Chrome developer tools window in order to look at a page's JavaScript code I get this window in regular intervals:
When I click "wait" the window goes away but comes back soon after.
How can I get rid of this annoying message?
This happens on Chrome 32 on Windows, and on different websites (e.g. http://spiegel.de).
it does seem that the issue is with the 32.0.1700.102 version of Google Chrome.
I've got several users who are experiencing the problem. It only seems to happen when you are working with sites that open popups (the kind you want) such as opening and email in a new window in Google Mail.
Its seams like the latest update may have helped fix the issue(32.0.1700.102 m), or some users are reporting that the v33 beta does not have the issue. https://productforums.google.com/forum/#!msg/chrome/1PgURxP9_-k/It9TupoPEgQJ
Bug report here:
https://code.google.com/p/chromium/issues/detail?id=335248