I'm using Netbeans to develop an HTML / CSS / Javascript / PHP app. I find that when I make HTML changes, I need to 'clear browsing data' in Chrome before the changes show. I suspect it's actually the 'cached images and files' that need to be cleared rather than the browsing history. Can someone explain why is this? And is there a way to auto clear history when launching the browser from Netbeans? It gets a little tedious when testing the app to have to clear browsing history all the time.
Try using Ctrl (or Cmd) + Shift + R to make a hard refresh. If needed, you can do this:
Open the Dev Tools.
Click and Hold the Reload Button.
Click on the third option.
Note: You can use Incognito Window, which doesn't cache much often.
Related
I have recently changed web host providers, (from 123-reg to SiteGround) and have a HTML website. Now when I make a change via FTP through Filezilla, it says upload successful however I cannot see the change on my computer. The changes are there however, as when I test it via kproxy.com I can see the changes. I have tried clearing my browser cache several times and this has not fixed the issue. The changes can not be seen on my ipad/ phone, and also cannot be seen on another friends laptop and phone either.
Does anyone know what the issue is here? I have been using Filezilla for a couple years now and the changes have always been instant and seen just via a page refresh.
Any help would be greatly appreciated!
Try deleting any extension in your browser that could be hindering it e.g AdBlocker
OR
In your Chrome browser, open developers tools (CTRL + SHIFT + I).
Navigate to Application tab.
Choose Clear storage from the side menu
Hit Clear site data button.
Open up the dev console to the network tab. look at the request to see where the data is coming from. it could be stuck in your disk cache and to clear it
On your computer, open Chrome.
At the top right, click More
Click More tools. Clear browsing data.
At the top, choose a time range. To delete everything, select All time.
Next to "Cookies and other site data" and "Cached images and files," check the boxes.
Click Clear data
Whenever I clear browsing data (Ctrl + Shift + Del), all my snippets (Sources tab) stored inside Chrome Dev tools gets deleted. I have to recreate them.
I don't want this to happen, as long as I don't clear them myself.
How to preserve them indefinitely?
Thanks
bt
When you deleting your browsing data you can uncheck Cookies and other site and plugin data checkbox:
I'm using a managed C720 Chromebook. Developer mode and most things of that nature are disabled. Web filtering is enabled from the "Chromium M" extension. When I restarted my device, the extension was automatically disabled because "This extension reloaded itself too frequently".
Is it possible for me to recreate the circumstances that lead to that happening?
Yes, you can, there is a way:
1) You can try and do developer mode, and keep spamming CTRL + D + Forward Button.
2) Login normally, but keep on spamming those buttons, then change to like a guest wifi, or a slow one then CTRL + SHFT + BACKSPACE, and delete your history, and that should be it, if it doesnt work the first time it should work the second time.
go to chrome://inspect/#extensions
click on inspect under the chromium m extension
go to the console tab
type close(window)
When a site gets stuck in chrome with the 'loading www.site.com' status, Is there anyway to know which of the elements on the DOM is delaying the load? for example, it can be an external js file or image that is taking long time to load. I tried using the network tab in the DeveloperTools, but it only shows the elements already loaded and the time they took. I couldn't find a way to see which element is stuck.
I found a way that I'm not sure it works in all cases, but it did for me. I used the Timeline tab (now shown in the Performance tab), it's one of the tabs in Chrome Dev Tools.
Open Chrome Developer tools (F12 or CMD + Alt + I in Mac) and click the Performance tab
Make sure you drag the grey timeline bar all the way to the right, you want to see the most recent section of events so you can find what's getting stuck:
Check just down below the records sidebar. If you don't see this like in the capture below, try toggling the icons, there are different view modes. Now, going all the way down I found these. It doesn't look like that's going well. Obviously some kind of infinite loop in some random code:
I couldn't find out if it was an extension itself or some other bit of code. Clicking through I only could find // Copyright 2014 The Chromium Authors. All rights reserved..
Checking in Incognito mode clear of extensions, the website loads just fine.
I'd also advise to check the Console tab to see if there are were any errors that might cause the infinite loading thing. You'll often find clues there.
I am referring to the save feature in the 'Sources' panel of the Chrome Dev Tools. I have been using this feature for a long time in the stable release of Chrome, but after installing the build from the developer channel, I notice that once I have saved the file the first time, Chrome no longer prompts me to save and just does it automatically after every change I make.
This is quite a pain, as I make a lot of changes experimentally in the dev tools whilst debugging which I don't wish to save, I would like Chrome to save the file only when I explicitly tell it to.
Does anyone know if there is a way to disable this automatic CSS saving?
(Apologies for no screenshot, my PrtScn key seemingly won't operate when I am in a context menu)
Update:
I have reverted to the current stable build, 27.0.1453.93, and the behaviour appears to be the same.
I am having the same problem, I can only offer workarounds: use another browser, such as Firefox, for doing tests!
Alternatively you could launch another instance of Chrome with a different profile. You could also launch a Chrome "Incognito Window", it seems to not apply the filesystem mappings.
I normally use an Incognito Window or inline styles to test changes.
Alas, I learned after reading a post by Google's dev relations person
that the automatic save cannot be disabled and it seems that's the way
it's going to stay.
html5rocks.com/en/tutorials/developertools/revolutions2013
– tommypyatt Feb 21 '14 at 14:22
While not solving the issue directly, it is a decent work around:
In Chrome, in the css inspector you can click and hold the + button, then choose to add your changes to the inspector-stylesheet. It's not as convenient as directly editing in your css-selectors, but what you write will all be in inspector-stylesheet.css, so not saved to your project. Then when you are happy with your changes, you can manually put them in to your css.