Safari Beta Updated

LenE writes "Safari has been updated to Beta 6, and is available via Software Update. New in this version is XML support, more speed, and many bug fixes. The download is 2.4 MB and doesn't require a restart." From the notes: "The Safari Update 2-12-03 improves the compatibility with popular web sites based on Safari user feedback, further improves the performance of loading web pages and Flash content, adds support for XML, increases standards conformance and delivers improved application stability. The update also enables access to web sites that offer self-signed security certificates."

Comments

Many bugs were fixed, and CSS improved *a lot*

[King Babar]

Yes, you can run the w3c.org CSS1 tests now. But more importantly from my perspective (:-)) is that Eric Meyer's css / edge stuff now almost completely works. The only abject failure there is the second "ragged float" demo, and even that one is pretty close.

As far as styling XML goes, your XML apparently does have to have the DOCTYPE stuff set up correctly. This means you get no joy with the stuff on the w3c Styling XML site; safari won't display the xml files there at all.

Oh yeah: it's a bit faster...not that you're likely to notice.

File size decreases

[wcbrown]

As noted by Bill Bumgartner, file size of the package has gone from 7.2MB to 6.9MB.

I haven't seen file size increase with upgrades. The Safari developers should be proud.

Shortcuts

[slenver]

Apple+arrows now work for back and forward pages..... I just hate having to reach for the mouse when browsing 'with one hand'.....

Re:You forgot to mention tabs, so I will.

[trouser]

Nobody *needs* tabs. But once I got into the habit of using them I found them invaluable and wouldn't want to return to tab free browsing.

Tabs allow me to group related pages in one window. eg. When I read Slashdot I often open interesting looking linked articles in the background, intending to read them once I'm finished with Slashdot. Sometimes I'd find these windows hours later, minimised or hidden, and wonder why I'd opened them and how I got there. Now they are all tabs in a window whose first tab is Slashdot. This makes the context obvious.

The same applies to use of search engines. Search for the thing that interests you, open each lead in a new tab in the current window. All search results end up opened in the same window and are therefore linked by context.

very useful memory aid. I'm not getting any younger.

Tabbed Windows solution

[Anonymous Coward]

Here you can see screenshot mock-ups of my idea for tabs:

http://home.quicknet.nl/mw/prive/dennis.scp/s/safa ri

The idea is NOT to add tabs inside a window. But to place a new window at the exact same place as your previous window and let any obscured windows pop up a tab.

So instead of indenting that new window to the lower right to reveal a clickable border as used today, I say let the windows behind the current window pop up a tab to show their name and icon. The windows stay independent and the screen has less clutter than with today's jumpy stacking system. Power-users can cycle the windows in a tab-like fashion using the [option] key.

Rendering engine changes in detail

[ollie_ob]

Mark Pilgrim's excellent blog Dive Into Mark has a very comprehensive list of changes to the Webcore rendering engine. The permanent link is here. I'm impressed with how quickly he's managed to list these changes seeing as it only came out today!

One change I've noticed is Safari no longer freezes for a minute when loading certain webpages. Another nice change is that stylesheet change on Dave Hyatt's weblog actually works now. Dave is ironically one of the Safari developers, so it's just as well!!!