Comments on: WebKit Fixes in Safari 2.0.1

By: Nate Koechley’s Blog » Blog Archive » Safari Browser Continues to Improve

Tue, 04 Oct 2005 16:54:37 +0000

[...] tinues to Improve

In Safari browser news, they’ve recently announced a long list of fixes to the WebKit rendering engine and a renewed focus on JavaScript and DOM Compatibility [...]

By: natekoechley

natekoechley — Tue, 04 Oct 2005 16:19:21 +0000

Hello,

I wanted to take a moment to thank you. It’s great that you’re communicating your progress. This level of information is valuable, and helps me provide the best experience to Safari users. It’s clearly a Good Thing that you’re fixing bugs and creating an ever-better product, but I wanted to write to commend you on the communication first and foremost. I’m a developer at a large web site, and knowing what you’ve addressed in each release makes it much easier for me to create for Safari.

I believe in a vibrant and varied ecosystem of user agents, and this transparently into features, fixes and issues is critical to that end. I want to deliver a delightful experience to Safari users, and this information makes that possible. Please strongly consider continuing to share this information in the future.

Thanks, Nate

By: ckizer

ckizer — Sat, 01 Oct 2005 07:01:15 +0000

You can see a demo of the fix here:
http://www.courtkizer.com/movies/webkit_builds_fix.mov

By: ckizer

ckizer — Sat, 01 Oct 2005 06:35:09 +0000

The best fix by far is the insert into textedit. Do you realize how HUGE this fix is? Every WYSIWYG editor, and every forum software on earth lets you use WYSIWYG tools to set styles, now they work properly because Safari supports moving where text is inserted. This is a HUGE leap forward. It means all those forum, toolbars work, and now a host of WYSIWYG web based editors, and many tools can be used with Safari!

Thanks!

By: vnoel

vnoel — Wed, 28 Sep 2005 18:38:50 +0000

Are any of the memory leak fixes mentioned in the previous post present in this release ? Or do we have to go get nightly builds if we want the fixes ?

By: ap_kelly

ap_kelly — Mon, 26 Sep 2005 07:35:58 +0000

Doesn’t supporting none standard features from IE weaken the whole concepts of standards? I mean, these none standard features will never go away if we keep supporting them. If they ever become standard then we should obviously support them, but I think this move just gives more power to IE, and less freedom to others.

Keep up the otherwise excellent work.

Andy.

PS: When will we see the acid test compliant version of Safari released?

By: gyoung

gyoung — Wed, 21 Sep 2005 00:20:01 +0000

Hiya - thanks for the posting. Just wanted to say that this kind of run-down of features and fixes is hugely valuable to web developers. Perhaps there’s another place this list is posted (and I’d be happy to check it out) but in the past I’ve not found it. So if you don’t do it on the blog, where will this kind of list live in future? TIA.

By: jan

jan — Tue, 20 Sep 2005 12:17:29 +0000

>> Fixed bug where progressive loaded background images would scroll down (no, that wasn’t on purpose).

Can we have it on purpose then? It just looks too good

Keep up the good work,
Jan
–

By: nettles

nettles — Mon, 19 Sep 2005 04:51:18 +0000

I should have added, that the former has the effect of generating a Drop
Down element when viewed in Safari, while the latter displays the code
fragment as intended.

By: nettles

nettles — Mon, 19 Sep 2005 04:49:56 +0000

Just a note on the XML you are generating for the atom feed, since I want it to be as pretty as can be!
When I read the page at through the Atom feed, the fourth bug fix gets written as:

While over here directly in the blog, it is encoded as:
<select></select>

–Ben