6 ms·

I don't think it's really fair to brag that your browser is the fastest when it willfully breaches the HTTP spec just to appear better than the competition. Is

by ZoFreX 14y ago

I don't think it's really fair to brag that your browser is the fastest when it willfully breaches the HTTP spec just to appear better than the competition. Is Chrome really better than IE, from an intentions viewpoint? Also worth noting that Chrome does (or at least, did) cache items even that it is explicitly told not to if they are CSS or JS which can be absolutely infuriating.

mey 14y ago
Had this issue when developing a real-time dashboards but didn't use websockets, jQuery kindly provides an option that will attach a random number as a query parameter forcing Chrome to round trip.
dspillett 14y ago
> Also worth noting that Chrome does (or at least, did) cache items even that it is explicitly told not to if they are CSS or JS which can be absolutely infuriating. I've certainly noticed it breaking the "ctrl+f5 refreshes everything" convention in recent versions, which can be a pain when testing new code and may cause problems for users on the release of new code if you don;t vary filenames (or other parts of the request). This is for script included using a simple <script> tag, not something that is loaded dynamically, so that isn't the cause. The solution I've used is to either close and reopen Chrome (yep: close all windows and restart, Google is becoming the new Microsoft in this manner!) or load the script file in a different tab and hit ctrl+f5 there first (it obeys the refresh then, and updates the memory cache that other tabs are using too).
- mjdwitt 14y ago
  I may be mistaken, but I believe that Chrome uses ctrl+shift+R to refresh everything.
  - idupree 14y ago
    It's "Ctrl-Shift-R twice". Hit it, wait a few moments for the page to start reloading, then hit it again. Otherwise it doesn't reload everything. Verify this by watching the Developer Console's Network section. I can only assume this is intentional; my coworkers told me this trick last year and it still seems to be the case.
    - SquareWheel 14y ago
      From watching the developer tools network tab it looked like Chrome respects Ctrl+F5, but I've also had the nagging feeling that two refreshes are sometimes necessary, and I've made that a habit when testing changes. I thought I was just being silly though. Would a browser really ignore Ctrl+F5 in the name of speed? That doesn't seem logical to me.
    - jberryman 14y ago
      You can turn off cache in developer tools, which has saved my sanity. Nothing else is consistent.
      - city41 14y ago
        Even then I find Chrome still caches. I've gotten in the habit of doing cmnd-shift-delete, which takes you straight to the clear cache settings. Sadly the equivalent command in Windows (Ctrl-shift-delete) does not work. I still feel Chrome is the best browser, but that's more to do with the lousy competition than Chrome's own quality as of late.
        DeepDuh 14y ago
        Try the new safari. I've been a Chrome user for quite some time, since the retine MBP I'm forced to use safari (for retina support). Since ML it has actually become quite pleasant I have to say. I don't see any clear advantages of chrome anymore in terms of functionality (I still like its interface better though).
        city41 14y ago
        The new Safari does look nice at initial glance. What worries me about it is WebGL is not enabled by default, and its JS engine is much slower than Chrome's. I mostly do WebGL game dev for my personal projects, and so I don't support Safari (since I can't expect people to have turned WebGL on).
        14y ago

by ZoFreX 14y ago

mey 14y ago

Had this issue when developing a real-time dashboards but didn't use websockets, jQuery kindly provides an option that will attach a random number as a query parameter forcing Chrome to round trip.

dspillett 14y ago

> Also worth noting that Chrome does (or at least, did) cache items even that it is explicitly told not to if they are CSS or JS which can be absolutely infuriating. I've certainly noticed it breaking the "ctrl+f5 refreshes everything" convention in recent versions, which can be a pain when testing new code and may cause problems for users on the release of new code if you don;t vary filenames (or other parts of the request). This is for script included using a simple <script> tag, not something that is loaded dynamically, so that isn't the cause. The solution I've used is to either close and reopen Chrome (yep: close all windows and restart, Google is becoming the new Microsoft in this manner!) or load the script file in a different tab and hit ctrl+f5 there first (it obeys the refresh then, and updates the memory cache that other tabs are using too).

mjdwitt 14y ago
I may be mistaken, but I believe that Chrome uses ctrl+shift+R to refresh everything.
- idupree 14y ago
  It's "Ctrl-Shift-R twice". Hit it, wait a few moments for the page to start reloading, then hit it again. Otherwise it doesn't reload everything. Verify this by watching the Developer Console's Network section. I can only assume this is intentional; my coworkers told me this trick last year and it still seems to be the case.
  - SquareWheel 14y ago
    From watching the developer tools network tab it looked like Chrome respects Ctrl+F5, but I've also had the nagging feeling that two refreshes are sometimes necessary, and I've made that a habit when testing changes. I thought I was just being silly though. Would a browser really ignore Ctrl+F5 in the name of speed? That doesn't seem logical to me.
  - jberryman 14y ago
    You can turn off cache in developer tools, which has saved my sanity. Nothing else is consistent.
    - city41 14y ago
      Even then I find Chrome still caches. I've gotten in the habit of doing cmnd-shift-delete, which takes you straight to the clear cache settings. Sadly the equivalent command in Windows (Ctrl-shift-delete) does not work. I still feel Chrome is the best browser, but that's more to do with the lousy competition than Chrome's own quality as of late.
      - DeepDuh 14y ago
        Try the new safari. I've been a Chrome user for quite some time, since the retine MBP I'm forced to use safari (for retina support). Since ML it has actually become quite pleasant I have to say. I don't see any clear advantages of chrome anymore in terms of functionality (I still like its interface better though).
        city41 14y ago
        The new Safari does look nice at initial glance. What worries me about it is WebGL is not enabled by default, and its JS engine is much slower than Chrome's. I mostly do WebGL game dev for my personal projects, and so I don't support Safari (since I can't expect people to have turned WebGL on).
        14y ago