There are a couple of reasons:
-
Assumed JS will screw up
Then you end up in an unstyled page (cause CSS isn’t loaded).
-
Browser
There had been an experience in the past which leaded to this “rule”. I think it was a minor number of Firefox.
-
Loading issues
JS is the monolith. You force heavy loading before small loading. The other way round, you’l ensure that “full rendered” comes before “full function”.
It’s always better to have “content” first and function later. Cause in this case you can view and read which is preferably the main aspect of web-design. Think of the electric toothbrush. If power fails, it’s still a toothbrush.
Cheers
Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at: