Comments on: The FOUC Problem http://webkit.org/blog/66/the-fouc-problem/ All about WebKit development Fri, 25 Jul 2008 13:04:18 +0000 http://wordpress.org/?v=2.6 By: JonathanAquino http://webkit.org/blog/66/the-fouc-problem/#comment-18377 JonathanAquino Sun, 25 Feb 2007 07:47:06 +0000 http://webkit.org/blog/?p=66#comment-18377 I think I've found a simple workaround: first CSS file just hides the body; last CSS file just shows the body. More info at http://jonaquino.blogspot.com/2007/02/workaround-for-safari-fouc-bug.html I think I’ve found a simple workaround: first CSS file just hides the body; last CSS file just shows the body. More info at http://jonaquino.blogspot.com/2007/02/workaround-for-safari-fouc-bug.html

]]> By: humorlessbitch.com » Dave. Dave. What Are You Doing, Dave http://webkit.org/blog/66/the-fouc-problem/#comment-13227 humorlessbitch.com » Dave. Dave. What Are You Doing, Dave Thu, 23 Nov 2006 10:52:14 +0000 http://webkit.org/blog/?p=66#comment-13227 [...] ptember 14, 2006 at 11:47 pm · Filed under the handbasket Uh, Dave? Whatever you wanna call it, and however interesting, the question of what t [...] [...] ptember 14, 2006 at 11:47 pm
· Filed under the handbasket

Uh, Dave? Whatever you wanna call it, and however interesting, the question of what t [...]

]]> By: cian http://webkit.org/blog/66/the-fouc-problem/#comment-12485 cian Tue, 31 Oct 2006 21:39:30 +0000 http://webkit.org/blog/?p=66#comment-12485 The Nokia E61 (which runs WebKit) does a lot of FOUCing actually, I wonder if this will be fixed with a nokia upgrade... The Nokia E61 (which runs WebKit) does a lot of FOUCing actually, I wonder if this will be fixed with a nokia upgrade…

]]> By: hyatt http://webkit.org/blog/66/the-fouc-problem/#comment-12094 hyatt Mon, 18 Sep 2006 06:14:34 +0000 http://webkit.org/blog/?p=66#comment-12094 humorless, not sure why you can't upload files. Do you have any Safari extensions installed? You might try uninstalling them if so. humorless, not sure why you can’t upload files. Do you have any Safari extensions installed? You might try uninstalling them if so.

]]> By: humorlessbitch http://webkit.org/blog/66/the-fouc-problem/#comment-12091 humorlessbitch Fri, 15 Sep 2006 01:03:42 +0000 http://webkit.org/blog/?p=66#comment-12091 <strong>Dave. Dave. What Are You Doing, Dave</strong> Uh, Dave? Whatever you wanna call it, and however interesting, the question of what to render first and why—I was wondering if we could just fucking skip it and let Safari be the Bitch Queen she used to be? 'k? Dave. Dave. What Are You Doing, Dave

Uh, Dave? Whatever you wanna call it, and however interesting, the question of what to render first and why—I was wondering if we could just fucking skip it and let Safari be the Bitch Queen she used to be?

‘k?

]]> By: Emma Snowdon - Jewellery Website, Please review. http://webkit.org/blog/66/the-fouc-problem/#comment-12089 Emma Snowdon - Jewellery Website, Please review. Thu, 14 Sep 2006 01:27:44 +0000 http://webkit.org/blog/?p=66#comment-12089 [...] tyled Content or FOUC and there are workarounds for it. Flash of Unstyled Content (FOUC) Surfin’ Safari - Blog Archive » The FOUC Problem [...] [...] tyled Content or FOUC and there are workarounds for it. Flash of Unstyled Content (FOUC) Surfin’ Safari - Blog Archive » The FOUC Problem

[...]

]]> By: xenon http://webkit.org/blog/66/the-fouc-problem/#comment-12083 xenon Sun, 10 Sep 2006 18:49:50 +0000 http://webkit.org/blog/?p=66#comment-12083 @boult, that is a recent regression that has now been fixed in the latest nightlies. @boult, that is a recent regression that has now been fixed in the latest nightlies.

]]> By: alexking.org: Blog > Around the web http://webkit.org/blog/66/the-fouc-problem/#comment-12082 alexking.org: Blog > Around the web Sun, 10 Sep 2006 16:46:57 +0000 http://webkit.org/blog/?p=66#comment-12082 [...] e same way about T-Mobile: but if their service is bad, what use are they, even if cheap? The FOUC Problem - I avoid this by doing these kind of script calls “onload”. Who Writes [...] [...] e same way about T-Mobile: but if their service is bad, what use are they, even if cheap? The FOUC Problem - I avoid this by doing these kind of script calls “onload”. Who Writes [...]

]]> By: Red Sweater Links » Blog Archive » FOUC Off http://webkit.org/blog/66/the-fouc-problem/#comment-12077 Red Sweater Links » Blog Archive » FOUC Off Wed, 06 Sep 2006 14:18:16 +0000 http://webkit.org/blog/?p=66#comment-12077 [...] rigued by the conclusion that the problem is exacerbated by the prevalence of Google ads! Link. This link was tagged Geeky, Web, Apple. [...] [...] rigued by the conclusion that the problem is exacerbated by the prevalence of Google ads! Link. This link was tagged Geeky, Web, Apple. [...]

]]> By: heckenpenner_rot http://webkit.org/blog/66/the-fouc-problem/#comment-12076 heckenpenner_rot Tue, 05 Sep 2006 21:06:30 +0000 http://webkit.org/blog/?p=66#comment-12076 "In WebKit (and Gecko) all pages parse and execute script on the main thread (the UI of the browser renders and responds to events on this thread as well). Thus blocking the thread that JS is running on blocks everything except network loading." Oh right, I wasn't really aware of that; I mean, of the fact, that everything just runs in a single thread, namely the UI thread. In this case, I am curious on your opinion whether this model is still viable for the long run? In particular, if we expect even more scripting stuff incorporated into future web pages. People are already doing quite complicated computations on the client side. Stuff like parsing JSON strings, calculating spreadsheets, etc is already there and takes some time. And we can certainly expect a further shift of computations to the client side, I'd guess. I already see my rainbow spinning ... :) Are there any long term plans to change that model in WebKit? If so, what's the way to go? Native "page threads"? A rewritten JS engine with explicit control state? Or both? “In WebKit (and Gecko) all pages parse and execute script on the main thread (the UI of the browser renders and responds to events on this thread as well). Thus blocking the thread that JS is running on blocks everything except network loading.”

Oh right, I wasn’t really aware of that; I mean, of the fact, that everything just runs in a single thread, namely the UI thread.

In this case, I am curious on your opinion whether this model is still viable for the long run? In particular, if we expect even more scripting stuff incorporated into future web pages. People are already doing quite complicated computations on the client side. Stuff like parsing JSON strings, calculating spreadsheets, etc is already
there and takes some time. And we can certainly expect a further shift of computations to the client side, I’d guess. I already see my rainbow spinning … :)

Are there any long term plans to change that model in WebKit? If so, what’s the way to go? Native “page threads”? A rewritten JS engine with explicit control state? Or both?

]]>