I have used Chrome Developer tools for quite some time. I have a wide screen monitor and so I have the tools docked to the right. I frequently use the network tab to watch calls and see the raw response, and it used to display the content of the response below the list of requests.
This week it suddenly is showing it to the right, making both panels ridiculously narrow and impossible to see anything in either. I'm trying to figure out if I did something to change it or if a recent update to Chrome might have broken it? I'm using Chrome version 46.0.2490.80.
Related
So I noticed this bug while generating a report with lighthouse on a certain site. After finishing, I closed the inspector and clicked on a random link within the site e.g About Page, however there seems to be a black space left behind. I tried running this on several sites, on some sites it shows up, on some it doesn't. Stack-overflow is one of the sites where it does show up.
Is this an issue with google chrome or with the lighthouse plugin? I haven't tried any other web browsers such as Firefox as I don't know how to use their auditing tools.
Thanks
Image attached for reference:
EDIT: Pressing CTRL+SHIFT+I populates that blank space with the inspector tool
I am developing a static web app via React.js. I am using the google dev tool to inspect elements. In responsive design mode, everything is fine. However, when I select a specific mobile phone the footer element is not shown when I scroll to the bottom. However, it is visible on the console when ı inspect elements I can see the HTML info. I thought that maybe somehow I fixed the height for mobile devices or smt. Then I tried the firefox dev tool and I am able to see the footer. I have no idea which one is more realistic since I didn't deploy it yet. I deleted the history of browser before I tried.
More specifically; on the chrome dev tool when I select responsive design mode and change the resolution to 375x812 (same as iPhone X), I am able to see my footer. If I select iPhone x rather than responsive design mode, then I don't see it. It is more annoying that, both cases are okay for the firefox tool and I see my footer. So what is the problem ? Why two dev tools act so so differently for the same app and more importantly which one is true ?
Okay, I figured it out. There is a zoom option next to the width and height. It was 100% for my case, which should be "fit to window". I am leaving this dumb question here, it helps if any other beginner faces the same issue.
I'm working on a small website and I'm writing a website almost from scratch. I'm using Bootstrap 4 and I'm modifying only basic CSS.
Whenever I open the Chrome Devtools, the website completely flips out and it looks like it keeps reloading. The entire website only loads from localhost, however, the network tab keeps showing repeating requests to the saem assets, over and over again. The second I quit Devtools, the entire behavior stops. I've tried installing a cache killer, tried incognito, but the problems keeps appearing.
I'm also using Octicons, and what I have noticed is that when I manage to get the Devtools to at least stay focussed at the right part, the <i class="oi oi-chevron-right"> node keeps flashing in purple, indicating there is a change to that node. I can't open it and even just clicking on it won't help, the entire CSS keeps shifting in the inspector bar and it seems like something is making rapid changes. It appears that Chrome re-applies styling changes that I made a few days back, such as locally modifying the margin of an element.
I was able to work on the website just fine a few days ago, but even moving back in commits won't keep the problem from happening. I am starting to think it is a bug with Chrome, but I can not confirm this in any way.
Is there anything that is known to break Chrome's Devtools, that might explain this behavior, or is there a way to clear the cache of the Chrome Devtools specifically?
The "Changes" tab in Devtools reports that there are no changes, but the CSS I see on page makes me seriously doubt it. Removing the icons entirely does not seem to resolve the problem, so I think the issue lies elsewhere. Breakpoints are not triggered either.
I'm not sure but,
Have you checked the chromium extension program?
I am developing an app with Ionic (1 !) and using ionic serve to test it on Chrome. I'd like to display the iPhone's status bar (battery, time and connection) on Chrome dev tools device mode.
Any knows if Chrome can do this?
I don't think there is a way inside of chrome dev tools. I've tried to find a good solution for a while, it is in their own words only 'for a first approximation'.
You can though, create the device with your specifications, HERE's a more complete list of available devices, where you can also shorten the length to get the size without the space of the status bar (yeah, not useful for the latest gen).
To better QA on mobile devices, maybe try something like Blisk, BrowserStack, Slant...
Or if it's for a screenshot, try something free like responsinator.
gl
I'm running Ubuntu (12.04.1 LTS) using VirtualBox (4.1.14) on a Windows 7 host machine. It seems that, using Chrome (21.0.1180.89), CSS transformations are causing the browser to lock up in a strange fashion.
This can be tested using this page: http://benmurden.com/css3test/css3test.html
In short, it looks like the "content area" of the browser, that is, anything apart from the URL bar, tab list etc. stops rendering during or after a CSS transformation and becomes "stuck" on top of every other open process. I can still close the offending tab or the browser itself since that area of the browser is fully responsive. I can even switch to another process and it will be partially visible under the "stuck" content area on top of it.
I meant to take a screen cap to demonstrate this particular effect but after locking up Chrome in this way and switching to a text editor behind it, only the text editor was fully visible on the screen cap and the locked-up Chrome was nowhere to be seen. This leads me to believe this might be a problem with VirtualBox rather than Chrome itself. Then again, there is someone sitting next to me with a nearly identical setup: Same type of machine running Chrome on Ubuntu using VirtualBox with identical versions of those three and he does not experience this issue.
I am unable to reproduce this on any other browser and host/guest combination I'm currently using. Those are:
Firefox (15.0.1) on Ubuntu
Firefox (15.0.1) on Windows 7
Chrome (21.0.1180.89) on Windows 7
Please let me know if there's any other information I could supply that would be of use.
Thanks!