But for someone stumbling into this blog, I thought it would be worth mentioning, it can be a good fit for the right sites and it’s not quite as involved as our previous discussion.

To be honest with you, I actually like the effect better so long as the pause is short – because with all of the methods we’ve discussed to this point, there is still content… and then more content. Even if not an actual font change, it is still a distraction. There is a certain cleanliness to having it all appear at once.

(On the other hand, the same effect can be created with the first methods we discussed if you wanted, though I’m not sure to what resouce expense).

As for javascript, for me it’s always about SEO, and making sure the search engines pull what I need. Even though there are some devices that default to JS off, they are going wayside as we type. Whatever methods are used, if seo is a consideration then just make sure the SE’s are able to see what you want them to see and all will be well…

Cheers…

The problem with it is that if you got something that loads and isn’t needed for the page to work (say a slow call to Google Analytics, Adsense or some bookmarking stuff) it will serious delay the rendering of the page.

I still find this to be somewhat of a non-issue due to the fact that javascript is just SO.. available. According to W3C 95% of visitors had javascript enabled in the year 2008. That’s 3 years ago. The discussion is nice though. :)

Btw: You forgot to close your CODE-tag. Fixed it.

I didn’t even think about it because all of our sites are designed around custom web applications, not semi-static web pages.

simply add this to your css:

This hides the entire display, then spits it out completely built. In IE, it means a second or two of nothing, then wham, there’s your page.

Of course, it eliminates the DOM issue, as well as the missing text with JS off issue.

I can’t use this effectively, because our custom web apps load in segments – so we need to have certain elements appear as the page loads. (If we did use this, the pause in IE becomes way too long).

But it could be an effective alternative in the more mainstream environment of semi-static web pages, and it’s a lot easier to implement than the solution I ended up with for my own needs.

Can’t speak for cross browser on this one, as I abandoned it before I got to that point.

Cheers

Cheers

As for Cufon, I agree 100%. It’s the best imperfect solution of the moment, ready to be unseated… though like many cross-browser technologies with a position of prominence, it will likely be a slow and heavily debated death… ;-)

Cheers

Doing it the *right* way is always good, however i feel that Cufón is a bit of a dying breed even though CSS3 has serious rendering issues in my opinion. Or… i haven’t seen anything better that look similar in all browsers… yet.