Currently I'm working on a big revision of the Events Compatibility Tables. And no the new table is not yet online because I'm not ready yet.
Testing event support is really awesomely complicated. I've been working steadily for two weeks now, and I still find new bugs and oddities daily, and twice on Sundays.
In any case, I discovered something remarkable when I studied the mousemove event. It sheds light on the way browser vendors keep track of each other's implementations nowadays, and on things that can go wrong.
Update: The bug described in this entry is an OS problem, and not a browser bug.
continue reading
Well, I've been using Safari Windows for a few weeks now, and I though it's time for a report. This report is only about the Windows version, because I can't install the Mac one. Why not? Because I don't have the right OS X version.
continue reading
Yesterday I downloaded Safari 3.0 Windows as soon as I found out it was available. It looks fine. Below you find a list of CSS changes, as well as a curious bug that appears on a minority of Windows systems.
continue reading
Apple just released Safari 1.3.1 without fuss. I found one important improvement over 1.3: the unload event, which was badly broken in 1.3, is now restored to its ancient reliability.
I didn't find any other significant updates in the CSS or JavaScript handling, but I did only a few very quick tests. If you found a change, please leave a comment.
Update: Safari used to download images with display: none only when they, or their parent element, were toggled to display: block. Unfortunately version 1.3.1 (and maybe 1.3) reverted to downloading the images anyway. Test page.
Two days ago Apple's team launched Safari 1.3, being part of the OS X.3.9 upgrade (once again named after a fierce predator, but I forget which one). Despite numerous bug fixes, the new release is marred by extremely serious onunload problems.
continue reading