Safari shows site with no design, layout or even CSS?

(Lyndon) #1

I can't figure out what this might be. The site displays perfectly as it should most of the time on most computers.

 

However, on some, the site just displays its contents with no CSS applied whatsoever, in Times New Roman with underlined blue links.

 

Worst of all, its the editors for the company that the site is for that often seem to have this problem in their office. It has happened to a couple of computers in the office, but not all of them, and they've had their network people look at it and it doesn't seem to be any kind of a proxy or network configuration that could be preventing anything coming through.

 

This problem may be exclusive to Safari. I am not entirely sure, but I believe the people experiencing this problem are using Safari, and when I try to view the site in it, I am presented with the unstyled content.

 

Is this a problem others have had? I know about the input boxes not working in webkit browsers, but is this familiar to anyone?

(Scott Hall) #2

Hello

 

Can I confirm that the users who are having issues in Safari actually have permissions to the design/css files i.e. do you have special permissions applied to these assets, or are they all public read access?

 

Some other checks that might be worth doing:

 

  1. Do your CSS files pass validation without any big parsing issues?
  2. A long shot but does your CSS file start with a character encoding declaration at all? I know this used to cause Safari to spit the dummy along time ago, as Matrix would render slightly broken CSS file output if something like (@charset "UTF-8";) existed at the very start of the CSS document. The output would be in other browsers as well, but Safari didn't react well.
  3. Is the HTML valid?
  4. Is the page rendering in quirks mode instead of standards mode, issues in html and css can force a browser to do this - http://stackoverflow.com/questions/627097/how-to-tell-if-a-browser-is-in-quirks-mode
(Tim Mcqueen) #3

If what Scott said doesn't solve it...

 

Sometimes we find that our browsers will occasionally decide not to read the CSS/design of the webpage. When this happens, we clear the cache and re-open the web browser, and it works fine (clearing the cache being the key). Not sure why the browser doesn't load it properly in the first place, but this still occurs sporadically for us (although we don't use Safari.)

 

Hope you find a solution.

(Lyndon) #4

Hey, thanks very much for your responses. After some more inspection, it is actually a permissions issue - the editors who are having this trouble are using accounts with restricted permissions, and I got the same symptoms in Safari because I had logged in with one of those restricted editor accounts.

 

I have been going through and "making live" and setting the read permissions to public for all of the assets on the site, but is that actually necessary? It's probably irrelevant for me at this stage (everything will need to be live and public shortly anyway) but for the future should I assume that all of the assets need to have their Read Permission set to include any user group that will even just be looking at most of these assets of the frontend?

 

I hadn't realised it was all so very secure back here! I'm not complaining - it makes sense now that I understand where I've been having trouble.

 

Again, thankyou for your help. Hopefully anyone else silly enough to have this problem will find this thread in the future!