Hi - title says it all. I'm working on a website and I make a change to the CSS file but safari stubbornly refuses to render the change. I was finding the same problem with Chrome until I added added a parameter to my file call thus: I'm testing in Chrome and Safari on Mac, and Chrome and IE on Windows 7. Of the four, Safari is the only one that won't reload the CSS! Obviously this doesn't matter much on my machine, but is there anything I can do in my code to force my viewers' machines to reload the CSS?
Thanks, David. I am a retired webmaster. From my experience it is unlikely to affect your users as, hopefully, they will not have to cope with frequent css changes. In some development environments it is not easy to determine which cache is causing difficulties.
Some browsers used to be very reluctant to update cached images or scripts. On several occasions I resorted to to your parameter=1 device but with a date/time stamp. The first thing to try is clearing Safari's cache on the Safari menu. Next try reset on the same menu. Can I assume that, since other browsers work OK, you have eliminated server caches? Some browsers work better interfacing with servers rather than local files - are you testing with local files or a server?
Hi The first thing to try is clearing Safari's cache on the Safari menu. Next try reset on the same menu. Yup those works for ME, but it's how others see my site that I'm concerned about. Can I assume that, since other browsers work OK, you have eliminated server caches?
I'm not sure what that means. Is this on my end or on my viewers' end? Some browsers work better interfacing with servers rather than local files - are you testing with local files or a server? On a server thanks for the reply.
This indicates that the problem is with your Mac Safari and not the server cache. There are two easy solutions: 1 - Don't publish pages or css until they are completed. You can still put them on the server but with unpublished names. Then when perfected change the name (or location) so that the public can find them. 2 - Change the css name or location after changes. This is more useful for changes to historic pages especially if the css is not called by many pages.
If you ask Chrome a question, you’ll see instant results. If you search for a particular website and it’s open in another tab, Chrome 69 will now offer to switch to the other tab.
I have AFP access to my server and can easily make mass changes to thousands of live pages with BBEdit lite so, on the rare occasion it is necessary, I can quickly change css etc names across a whole site or the whole server. Apple Footer. This site contains user submitted content, comments and opinions and is for informational purposes only. Apple may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site.
All postings and use of the content on this site are subject to the.