Strange Safari artifact? Topic is solved

[gfroyle]

Newbie here shopping around for a simple CMS, so not surprisingly was led to consider CMSmadesimple.

But one thing about it seems weird - using Safari (v2.0.4) I get a very annoying artifact whenever browsing the CMSms site itself - every time I navigate to another page, I get the un-formatted version of the page displayed for perhaps half-a-second before the CSS is applied and the page is properly formatted.

Doesn't seem to happen on Firefox (also on MacOS).

Is it me (or some preferences that I have misconfigured?  Or is it this site? Or is it something about CMSms itself?

Thanks

Gordon

[Elijah Lofgren]

Newbie here shopping around for a simple CMS, so not surprisingly was led to consider CMSmadesimple.

CMS Made Simple is the best CMS that I have found. Glad you found it too.

But one thing about it seems weird - using Safari (v2.0.4) I get a very annoying artifact whenever browsing the CMSms site itself - every time I navigate to another page, I get the un-formatted version of the page displayed for perhaps half-a-second before the CSS is applied and the page is properly formatted.

This also happens in Opera because Opera starts displaying the page before it loads the stylesheet. However, it does not happen on subsequent pages, I assume it caches the stylesheet and uses that.

Doesn't seem to happen on Firefox (also on MacOS).

Is it me (or some preferences that I have misconfigured?  Or is it this site? Or is it something about CMSms itself?

I've never used Safari, but you may want to check and make sure that  you have Caching enabled.

It seems that the problem you are having is because the stylesheet takes a bit longer than usual to load.
Showing the page without styles seems to be referred to as a Safari bug:
http://www.hopstudios.com/nep/unvarnish ... d_content/
http://www.ifingers.com/tips/2006/01/fouc-safari.html
http://weblogs.mozillazine.org/dave/arc ... tml#002840

Hope this helps,

Elijah

[Ned Nowotny]

I started having this problem as well.  It is described as "Flash Of Unstyled Content" (FOUC) and can be a problem for different reasons in Safari and Internet Explorer.  To fix the problem in Internet Explorer, see BlueRobot.  For Safari, I have not found a fix to date, but you can make the problem less noticeable by using CSS to hide the document body when loading the page and then making the body visible in the style sheet.  For example, add a style attribute to the body element like this:

Code: Select all

</__body style="visibility: hidden">

Then include a rule like the following in the associated style sheet:

Code: Select all

body { visibility: visible !important; }

Note that the style sheet rule must be marked "!important" to ensure that it overrides the style specified in the HTML document.

The result of this change is a that the flash of unstyled content is replaced with a flash of a blank page, but this is far less disruptive and may not even be noticed in most cases.

I found this work-around described in the last comment to Safari FOUC (Flash of Unstyled Content).  (You have to scroll right to find the comment on this very unconventional page.)