With the recent release of Safari 3.1 the WebKit team has completely reworked the handling of key events. John Resig has an interesting blog article with some details. Safari 3.1 now behaves pretty much like Internet Explorer and is in general much more sane than before. For instance, all those strange key codes larger than 64000 for special keys are gone and finally modifier keys like "shift" and "control" fire key events as well. Interestingly, Safari is now the first browser to support the key identifier property defined in the DOM level 3 event specification. In qooxdoo we already emulate this property in key events for quite some time now, and it really helps to simplify key handler code in our widgets.

Unfortunately, this change in Safari 3.1 broke the existing qooxdoo key event handler. But it is already fixed and available in our subversion repository for legacy_0_7_x branch and trunk. The fix was basically to detect the current WebKit version and use the existing Internet Explorer key handler code also for Safari 3.1 and above. Since all browser quirks are handled separately this was a pretty simple fix. Of course, it will be part of the next minor release 0.7.4 as well as the final 0.8. If you need Safari 3.1 support now, please checkout the latest version from the legacy_0_7_x branch.

Thanks to Hugh's and Andreas Junghans' investigation we have fixed a Internet Explorer specific memory leak. We suggest that all users of the 0.7.x-line should update the file qx.io.remote.XmlHttpTransport.js as soon as possible.

For SVN users of the trunk and legacy_0_7 folders this file has already been patched. A simple update of the repository should be enough for them.

Download corrected file: Fixed XMLHttp transport layer for 0.7.1 + 0.7.2

As there were no other changes to this file since 0.7.1 came out you can use this file for both qooxdoo 0.7.1 and 0.7.2. Users of older versions - especially 0.7 and 0.6.x should update to 0.7.2 as soon as possible. There were a lot of other improvements, too.

Please make sure that you re-run "make" after you have updated the file. Sorry for the inconvenience.

Thanks to Dietrich Streifert we just became aware of an issue introduced with Firefox 2.0.0.1, which is was made available today. The problems occur for qooxdoo releases 0.6.2 and 0.6.3 only. The DOM-based source loader introduced in those two releases is XHTML compatible and seems to be incompatible with the changes of this Firefox version.

We have changed the default loader in SVN with revision 5423. Please note, this change breaks the XHTML compatibility in the source version of all qooxdoo-based applications. You can apply the hotfix which is attached to the bug to your qooxdoo SDK or simply update your tagged SVN checkout (both tags were updated accordingly). Otherwise just wait for qooxdoo 0.6.4 which will also include this fix. Sorry for any inconvenience.

I've just registered and configured a new mailing list, which is used to monitor the bug activity. Bugs in qooxdoo are also used to manage feature additions and enhancement wishes.

You can register yourself to always stay up-to-date with the further development of qooxdoo.

To fulfill the requirements for a bug-tracking tool for qooxdoo, we have finally installed a fresh bugzilla to bugzilla.qooxdoo.org. After you register yourself, you can enter your bugs there.