Labels

WebKit Success!

Well, it only took uber-hacker Alp about 5 minutes to figure out the problem I had that was causing the blank-box fonts in WebKit (see below). Once he pointed out my problem (a stubbed-out "GlyphPage::fill" method), I was able to dredge up old Apple code, convert it to the current code base, and away we go.

Patch attached to this.
Labels:

Comments

quiris said…
The biggest challenge now is porting text effects like text-shadow ;)
12:26 PM
Unknown said…
I don't think you quite realize how important this is. My gut feeling says that although WebKit doesn't yet have as much momentum behind it as Firefox does, it's got a lean and mean codebase which means hacking it is much faster -- not to mention getting up to speed with it (I shudder at the thought of actually having to dig into the Firefox codebase). What this means is that WebKit's development can potentially be multiple times faster than Firefox. And we all know it's already faster and less memory hungry than FF, so it could be a major player in the Windows browser market.

A lot of people, myself included, are turned off by Safari because it doesn't look or work like a Windows application -- much like the initial resistance towards Mozilla (Seamonkey) which led to FF's eventual creation. If you can pull off the same with WebKit, we'll have a very fast and lean browser, consistent with the rest of the Windows UI, with the advantage of speedy development.

I can see such a browser gaining a significant market share. I wish you godspeed.
2:22 PM
Post a Comment

Popular Posts