Opening Devtools on Chrome makes entire page trip - html

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?

Related

Chrome Bug!? - infinite scrolling above page body (several Pages)

I recognized this Bug on several Pages occurring in Chromium related browsers. I opened up a Chromium Issue, where the project members could not reproduce the problem - I am trying to figure out why this is happening (since the Problem occurs on Pages as like google.com, amazon.com, and so on, on several Mac-OS devices, which have nothing else in common) - we tried it on a clean Chrome installation, where The Problem is also occurring. To me it seems to be a bug - now I'd like to know if other people are also not able to reproduce. If you can reproduce (to reproduce read the following lines below) and/or find something new/interesting about the problem consider supporting the Ticket/Chromium Issue.
Chrome Version
91.0.4472.101 (Offizieller Build) (x86_64)
URLs tested
https://www.google.de/
https://www.microsoft.com/de-de
https://www.amazon.de/
Other browsers tested
Safari: hasn't the problem
Firefox: hasn't the problem
Edge: has the same issue (also Chromium based)
Chrome Canary: has the same issue (also Chromium based)
How to reproduce the problem?
Refresh Page (Command+Shift+R) and Scroll upwards while page is loading or in parallel (you have to be quick to reproduce).
What is the expected result?
Expectedly the Page should not over-scroll and stop at the pages top/end instead the page can be scrolled infinite above the pages top, same issue appears by scrolling down, where scrolling should stop at the bottom of the page.
What happens instead?
Browser keeps scrolling above the pages top/bottom infinitively. Once triggered the infinite scrolling wont disappear, even after refreshing the page - the only way to change the behavior is to copy the url and paste it within a new tab.
Small update: it seems like the problem appears when using a logitech mx master mouse (if you run into the problem when not using this specific model, let the chrome people know) - it looks like it can be solved by following steps:
Open a terminal window.
Type in the following command then hit enter:
defaults write -g NSScrollViewRubberbanding -bool false
Source: https://www.computerworld.com/article/2726533/turn-off-elastic-scrolling-in-os-x.html
Hopefully they'll fix the problem in chrome itself, until then this should solve the problem.
Update: See Irgend Son Hansel answer
I don't think there's an official fix currently, but what I do when this bug comes up is to simply click the scroll bar. It usually fixes it for a while before it comes back up again.
I am not entirely sure what the OP is asking but I assume they are looking for a fix or a workaround for this?
I occasionally experience the same on my MacOS machine. For me, refreshing page does not work. What I do is the following:
copy url of the current page
open new tab and navigate to the same url
close old tab

Website doesn't display properly

The website I'm developing suddenly stopped working properly. The images on my Homepage appear sliced and in weird places (however when inspecting source and hovering over certain elements, the highlighted content seems to be in the right place), some hover on effects don't work and some text doesn't render.
Everything works properly in all other browsers except for Google Chrome. I cannot think of any other thing I've updated in the source code than executing svginjection plugin.
I uploaded my backed up files that used to work before, but the problem still occurs. It doesn't show up on every single computer, just on some (and I've checked it on multiple machines, both - Mac and Windows).
Just to clarify, I did clear the cache, I did check in the Incognito mode, I did restart my computer. None of these helped. I'm also 80% sure that problem only occurs on computers, on which this website was previously opened (the pattern I noticed after making around 10 tests at work).
Thanks for any help
Aight, so after going through all my files, trying to disable multiple options, etc... Everything is fixed now. If you do have similar problem, go through your css files and disable all webkit powered transforms and transitions, cause apparently enough is enough and if you have too many, Chrome just won't handle it. I managed to still reuse some of them, so... Must have caused some glitch in the matrix and that's why it all got messed up. For weirdly positioned images check z-index of parent container.

What can cause CSS styling issues on Chrome that are resolved when developer tab is toggled?

The HTML and CSS are rather large so I can't pinpoint the issue or post a good example. When I toggle through my UI, the css styling seems to break, the most jarring of which is that the background changes to grey. I was wondering if anyone encountered similar issues. Here are some of the conditions for me.
-Chrome: Firefox & Safari working fine
-Small Screen: Problem doesn't occur on larger monitors
-Toggling developer console on and off fixes the issue
It's difficult to try and pinpoint the issue without seeing some code or even a fiddle, but when you open the inspector the page is resizing, and so redrawing (at least some of) the elements. It's also possible that there's a cache issue - I believe by default when you open the inspector the cache is disabled and so all css and scripts are downloaded again. That said, if you aren't refreshing the page it with the inspector open its unlikely to be that.
My money would be on the window effectively resizing when you open the inspector, and so some (if not all) elements are forced the redraw and thus re-evelauate their styles.
Maybe you could use Chrome's timeline to check what is being painted as time goes by. Try running that and opening the inspector while its active to try and see whats going on.
Looks like a long standing bug (years) with webkit:
How can I force WebKit to redraw/repaint to propagate style changes?
The solution that appeals to me is:
$('#body').hide().show(0); from Force DOM redraw/refresh on Chrome/Mac
to force a redraw.

Why do images reload on refresh on one server, but appear instantly on another?

These two websites are exactly the same:
http://www.inandoutofwonderland.com
http://dev.zelencomm.com/inandoutofwonderland/
However, when I press F5 to refresh (or Command-R on Mac) the former website renders immediately and without any visible image loading, the page image does not even flicker or move in any way.
When I do this on the latter copy of the site, it goes to black, and all images disappear and visibly all reload from top to bottom.
The two websites are exactly the same in both files and database. I've tested this is Firefox, Chrome, Safari and Explorer both on Windows and OSX, and I have the same behavior everywhere. The two sites are on different servers, so I can only conclude this is some server setting I am unable to track down. The servers seem to have the same speed, it's just one makes the site reload its images on refresh while the other does not.
I have tried to add the "ExpiresByType" commands into the htaccess file on the 'slow' site but it does not seem to have any effect.
I would really like to figure out what the difference is so that I can make the latter website's server behave like the former and load its images up immediately rather than have the whole top-down rendering thing.
Thanks for any insight into this.

CSS Rendering Issue in Chrome / Firefox

I was trying to design this site:
http://bylc.org/summit2012/
When I was working offline in my pc everything was alright. But when I uploaded it in the server, the problems started to show up.
When I try to load the file for the first time everything seems to load correctly but after reloading the page the carousal stops working and the right part (side bar) of the page gets down and renders some text in different color and font. Also there becomes a little space between the carousal and the side bar.
I've tried everything in my knowledge. tried X-UA-Compatible, stopped all javascript in the page. But nothing did work. :( Could anyone please check and help.
Disabling scripts altogether caused the errors to occur on initial load as well as on subsequent loads, which leads me to believe it has something to do with the order of things loading in your page.
I suggest moving your script declarations from the head to just before your closing body tag to ensure they load as quickly as possible.