I realised today, that I'm no longer able to edit or create new cookies in Chrome. It works in Firefox and Safari as of now.
I go to Developer Tools > Applications > Cookies and try to change their values. The line turns red and if I click out, it resets to what it was.
Do I have to deactivate something somewhere?
yep, solved by:
search in chrome settings for flags by entering in the url field chrome://flags
search Partitioned cookies and set it to enable
Restart chrome (might need to refresh the page after the restart)
Related
I want disabled site-isolation in chrome so that I can see the cookie in request header easily.I Starting Chrome with the --disable-site-isolation-trials in the past.But when chrome version after 72.It becomes useless.How I can do in the newest chrome
Open chrome://flags/#enable-site-per-process and search for "Disable site isolation". If you're confident with Google and want to get more comprehensive guarantee, just choose Default.
Current version (Chrome 75) crashes when switching flag Disable site isolation to disabled, relaunch browser and open developer tools (aka. inspect).
I accidently checked the "disable alerts from this site" box in Chrome, and now I cannot get any window.alert to work on my localhost.
I have tried resetting the settings in advanced but no luck.
Close and re-open the tab. That should do the trick.
I can see that this only for actually turning the dialogs back on. But if you are a web dev and you would like to see a way to possibly have some form of notification when these are off...in the case that you are using native alerts/confirms for validation or whatever. Check this solution to detect and notify the user https://stackoverflow.com/a/23697435/1248536
In Chrome Browser go to setting , clear browsing history and then reload the page
So, I have a script called "engine", and after much headbashing and (futile) debugging, I've found out that GC simply isn't reloading it!
This is how I include it in the webpage (inside the <head> element):
<script type="text/javascript" src="engine.js"></script>
When a put 10 console.log("asdf");'s at the start of the script, it's like they aren't there. When I went to the "resources" tab in the GC console, I saw that no changes are being applied whatsoever to that script! Hlep? Would putting a + "?" + new Date() at the end help?
The universal solution that works in Chrome, Firefox and IE is cleaning the cache via Ctrl+Shift+Del (on Mac ⌘+Shift+⌫).
Chrome solution #1
Open Developer Tools (F12 or ⌘+⌥+i, or right-click → Inspect).
Select the Network tab and tick the Disable cache checkbox.
Reload the page.
❗️Note: The cache will be disabled only when the devtools window is open.
Chrome solution #2
This only makes sense if #1 is not used.
Open Developer Tools.
Click the Settings cogwheel icon in the bottom right corner.
In the dialog that appears, select under the Network subsection the Disable cache checkbox: from now on the cache will be skipped when the devtools window is open. When the devtools windows is closed caching will work as usual.
Chrome solution #3: empty cache + hard reload
Open Developer Tools (otherwise the menu in the next step won't show).
Click and hold down the Refresh button, and then select from the dropdown Empty Cache and Hard Reload.
Modifying javascript code
A browser-agnostic solution which could be used for debugging is to append in your server-side code a randomly-generated version string as a query parameter, i.e. call your script as:
<script type="text/javascript" src="myscript.js?ver=12345"></script>
This trick will force the browser to reload the script when the value of the ver parameter changes. If you make ajax requests then you can append "?ver=" + new Date().getTime() to your URL.
NOTE: Don't forget to remove the parameter when you are finished debugging because in production you most likely do want the scripts to be cached. It is a common practice though to generate a new timestamp on each new build — this can be used in production, and will ensure that after a new deployment the clients will always get the updated scripts.
Unlike all the above solutions this one will work even when you have some sort of caching (e.g. redis, memcached, varnish) or CDN (e.g. akamai, cloudflare, cloudfront, etc) between the client and the server.
It is possible that the script is cached so the old version is loading from cache. If you want to make sure you get a new version, you can force a browser reload, clear your browser cache or change the name of the script or put a different query parameter on the end of the filename.
This bugged me as well; CTRL+F5 or SHIFT+F5 never worked...
The only things that works is opening your dev tools (hit F12), and right-click the reload icon next to the address bar and then selecting either "Hard Reload" or "Empty Cache and Hard Reload"
As I said in the comment I guess it's a cache problem, a CTRL+F5 should be enough, in case it is not go for CTRL+SHIFT+CANC and clear browsing data. However sometimes it's the server that has some kind of cache, I say that because with IBM WebSphere I often get cache problems that I can't resolve with a simple F5 on my browser. I just have to wait for my web server to "refresh" itself.
In the latest chrome stable 21st Oct 2016.
Open Developer Tools (F12 or right-click > Inspect or vertical ellipsis icon in address bar right corner > More Tools > Developer Tools).
Click the vertical ellipsis icon in the top right corner of Developer Tools navigation bar > settings.
In the Preferences section find the Network > Disable cache.
I'm looking for the way to log stuff in Internet Explorer Developer Console that preserve page refresh.
Under Google Chrome and Firefox's Firebug it's an option for that, but I could not find it under IE.
I'm using IE 9.
In IE Developer Cosole go to Tools -> Clear Entries on Navigate and uncheck what you want to stay in log.
In Internet Explorer 11 there is now a button ("Clear entries on navigate") which one must toggle for enabling/disabling the IE to clear the network logs on navigation or even http redirect.
MSDN: http://msdn.microsoft.com/en-us/library/ie/dn255004(v=vs.85).aspx
In Internet Explorer 11 there is a button that you can click to delete or preserve console logs on navigation. If you want to preserve your console logs, then just untick the button (highlighted red in my screenshot).
Clear entries on navigate is a toggle switch with on and off states. When in the off state, network traffic for a window or tab is recorded continuously as the browser moves from page to page. When in the on state, recorded traffic is cleared each time you navigate to a new page. This is turned on by default.
Please note: Dev tools will close if the redirected domains navigate from a protected mode site to a non-protected mode site, e.g. from internet zone to intranet zone
Since I'm building a dynamic site, I need to track the changes between pages, ie. Ajax calls, POST, GET stuff and similar stuff.
I'm looking for the same functionality like in Firebug (where you can enable "persistent" and the console is not cleared every time you reload a page or submit a form.
So, my questions is: is there a way to make Google Chrome JavaScript console persistent?
(And if yes, how?)
Update: Copying the answer here, if anyone's still looking for this, Chrome 14+ has a setting in Developer Tools > Settings labelled "Console: Preserve log on navigation".
Update 2: the latest versions of Chrome (33+) have this option by right-clicking in the console.
Update 3 (late 2017): The latest versions of Chrome (60+) have this option by opening the console, clicking the gear in the top right corner and selecting "preserve log"
If anyone's still looking for this, I'm on Chrome 15.0.874.58 beta-m and I have a checkbox in Developer Tools > Settings labelled "Console: Preserve log on navigation". Does the job nicely.
at Version 67.0.3396.87 (Official Build) (64-bit)
Unfortunately, Chrome doesn't support that functionality yet, although there was talk in December 2010 about adding in the next major release...
This answer is no longer valid
As of Chrome Version 73.0.3683.86 (Official Build) (64-bit):
Click the ellipsis in top right of Developer Tools
Navigate to Settings > Preferences > Console
Check Preserve log upon navigation
Try this to enable console on popups
I had the "preserve logs" options enabled and still had the Console losing focus to the Sources tab. If that happens (apparently during debugging), it helps to disable "Focus sources panel when triggering a breakpoint" in "Settings > Preferences > Sources".
In Chrome v102
I opened Chrome Dev Tools,
I clicked on "gear" icon (Top right corner)
Enable "Preserve log" checkbox