I’ve noticed that there’s been a little bit of confusion out there about WebKit.

WebKit has always focused on performance, web standards compliance, security, and relatively understandable code.

Yesterday, Steve Jobs announced the iPhone, a new combination phone, iPod and internet communications device.

We don’t usually just repost content from other blogs here.

Digging up a very old blog entry from http://www.456bereastreet.com/archive/200408/sizing_monospaced_fonts/, the question is asked, “What’s up with the different font sizes when the monospace font family is used?” The answer, as usual with Web browsers, is pretty interesting (which is browser developer-speak for “insanely confusing”).

FOUC stands for Flash of Unstyled Content.

There have been a lot of exciting new engine-level features that have been added to WebKit over the last few months, and not all of them have received their own blog entries.

If you are reading this post, you have probably already noticed that we’ve launched a visual redesign of the WebKit site.

We’ve heard a number of reports of Safari memory leaks, and we’d like to fix a bunch of these.

Here are some name changes we’re planning for some classes and functions in JavaScriptCore in the KJS namespace: Old Name New Names ValueImp JSValue AllocatedValueImp JSCell ObjectImp JSObject Undefined() jsUndefined() Null() jsNull() Boolean() jsBoolean(), jsTrue(), jsFalse() Number() jsNumber(), jsNaN(), jsZero(), jsOne(), jsTwo() String() jsString() We want to take Imp suffixes off class names of subclasses […]

The new radio buttons are now enabled (along with checkboxes) in the latest WebKit builds.

The first of the new form controls for WebKit has just been turned on in the latest WebKit tree.