It was my first WWDC ever. Rich was there too! I finally got around to learn a lot about Dashboard Widgets and Webkit. Apple Engineers are a passionate, dedicated and relentlessly-working bunch. If you’re into helping out the open-source community for the Greater Good, you might consider heading over to the WebKit Open Source project. As you likely already know, it powers Safari and Dashboard Widgets. If you’re a web developer with strong HTML and CSS skills, and happen to find odd rendering issues in Safari, consider filing a bug and/or putting together a very simple test case you can submit to the project. They’ve put in place a very cool suite of automated regression testing, in which textual representations of a page’s rendering are saved into “Render Tree” files, and checked against with each WebKit iteration.
I’ve also learned that Safari 1.3 (and of course Safari 2.0 in Tiger) introduced support for “contenteditable”. The blogosphere has already been buzzing about it. If you’ve written-up some documentation about contenteditable, or have built a cool demo or working product, we’d love you to point to it in comments, and we’ll surface it in this post. Here’s the original announcement from Dave Hyatt. I’ve heard there are similar hooks in Gecko, could someone point us to them?
input type=”search” is also looking very promising, albeit still OS-X-centric for now. As Dave points out, this can still be coded in a cross-browser-compatible way. Regular browsers will see a normal text field, contents of which can simply be submitted to the enclosing form’s action. One cool feature is that we can trap a DOM “search” event (onsearch attribute if done inline) that gets triggered when a user is “done typing” if the “incremental” attribute is set, versus, say, the more typical “onchange” event triggered at each character being typed. The other attributes it defines are also looking very cool.
On a semi-unrelated note, i’ve got a couple of pics up on flickr.