webkit
Latest
DrunkenBlog discovers another image that crashes WebKit
Wanna have some fun with Safari (or apparently any WebKit-based browser), a certain picture, and a post at the DrunkenBlog? Apparently, drunkenbatman has come across another image that can crash WebKit and anything based on it, including the Finder and Preview.If you want the full rundown, head over to the DrunkenBlog post using something like Firefox, Camino or Opera - just not Safari, OmniWeb or any other WebKit-based browsers. If you visit the post in Safari, it will crash; this has been tested in the latest 10.4.5 update on both PPC and Intel versions. Also, whatever you do, do not download the image to your desktop, especially if (like me) you have the Finder option to "show icon preview" turned on. It'll crash Preview and send Finder into a constant crashing/restart cycle.Like I said, you can get the full, in-depth rundown (and I mean in-depth) on this issue and its specifics at the DrunkenBlog.
Top contributors to the Webkit Open Source Project get MacBook Pros
The WebKit Open Source Project is the open source component of WebKit (which powers Safari and is available for developers to access with their applications). It seems that lots of non-Apple programmers have been chipping in to do a number of things, including fixing bugs and what have you.Normally an open source volunteer is 'paid' with experience and the knowledge that she is helping out with a cool project. However, this time around Apple is giving the top twelve contributors to the project a brand new MacBook Pro, and five of them are going to attend WWDC (on Apple).Very cool, Apple. Now, when are you going to start handing out MacBook Pros to bloggers?
New WebKit Web Inspector
Check out the new HUD on the Safari WebKit: the Web Inspector. According to Surfin' Safari, "The Web Inspector lets you browse the live DOM hierarchy in a compact HUD style window, catering to the needs of web developers and WebKit hackers alike."It looks pretty cool, but you'll have to update your tree or download the nightly build to use it, and if you don't know what any of that means, perhaps you should just run along and play with the other kids on the Internets, mmm-kay?
Shiira 1.2 released
Wow, it really is a wonderful life. A new version of Shiira was released today, 1.2, with a ton of great new features. I had all but switched to Shiira a while back, when Firefox was too slow and Safari too annoying. But Shiira began to lag in the features department (particularly RSS support) and I had to drop it. Since the browser is based on Webkit, it makes sense to see some stuff now added: Universal Access support, Private browsing... And there are some unique features of Shiira, like the page transitions (sorta pointless, but fun to show PC lovers), and the incredibly handy Tab Exposé, which allows you to show all tabbed windows with a keystroke (why doesn't Safari have this?). One thing I really like about Shiira, however, is the ability to automatically use Safari bookmarks without importing, and it supports Firefox bookmarks. And don't forget the Shiira mini-browser.With the new RSS support, I can actually see using a browser as a feed reader. Maybe I was doing it wrong before, but the sidebar in Shiira makes a perfect companion to browsing. One nice little window on the side shows me new, unread stories as I surf. The less clicking, the better. The sidebar is really what got me to switch to Shiira to begin with, I just like having it available. It's a little redesigned in this version, and actually works better. Oh and did I mention Shiira supports themes?
Hunting Safari Memory Leaks
On the Surfin' Safari blog, the development team behind Safari are going on safari for memory leaks and they could use your help. If you are interested in playing around with WebKit, all you have to do is install the Developer Tools and grab a fresh build of the WebKit, enter in a few Terminal commands, launch Safari, surf, and then run another Terminal command (these instructions in detail are here). Then, of course, you will need to produce the most detailed bug report that you can: "If you want to make an even better bug report, see if you can reproduce the leak by following some specific set of steps, and include that in the bug. You can also look at the backtraces in the leak report and see if you can match up ones that look the same. Its useful to file a separate bug report for each one that looks different, and to consolidate leaks on different sites that look like they have the same stack trace."
