-
Notifications
You must be signed in to change notification settings - Fork 0
Release Notes 1.0.1
Release 1.0.1 of Dubsar upgrades to jQuery 1.4.4 and jQuery UI version 1.8.6, fixing a few related bugs and providing some optimizations.
November 19, 2010
- Upgrade to jQuery 1.4.4 This is the current stable release of jQuery UI.
- Upgrade to jQuery UI 1.8.6 This is the current stable release of jQuery UI.
- Use customized jQuery UI package Rather than the full, Google-hosted jQuery UI package, only support for the required components is included.
- Bundle jQuery scripts The minified jQuery and jQuery UI scripts are now bundled with the rest of the Dubsar javascript.
- Use jquery-mockjax plugin for QUnit tests This obviates the autocompleter requesting data during a QUnit test. Previously a race condition made the autocompletion test fail frequently.
- Unresponsive enter key Issue 1: When the autocompleter menu was visible, the search form would not respond to the enter key. This was fixed by upgrading to jQuery UI 1.8.6.
- Wrong cursor when dragging tooltip Issue 16: In some browsers, a text cursor would be incorrectly displayed when dragging a tooltip. This was fixed by upgrading to jQuery UI 1.8.6.
See Dubsar's full current list of open issues at https://github.com/jdee/dubsar/issues.
- Invalid inflections These have mostly been cleaned up. The remaining errors primarily involve verbs ending in a short syllable with l or s. The clean-up process continues.
- Missing inflections Some verbs do not list regular past-tense forms because of the presence of an irregular form. This requires review.
- Tabbing through the search form On some browsers, if focus is in the word-input field (tabindex 2), and you press TAB, focus is not properly transferred to the search button (tabindex 3). This happens in several browsers on OS X.
- Unresponsive autocompleter For example, type a, generating an autocomplete menu beginning with ask. Backspace to erase the input. Then type a again. You'll get no autocompleter. If you type b to make ab, then backspace, you'll get the autocompleter again.
- Autocompleter tests fails in Camino Apparently the jquery-mockjax plug-in does not work in Camino, Opera or Konqueror. Otherwise, Dubsar works well in the first.
- Back: opening the right accordion pane Dubsar's accordions work well when refreshing a page, which happens in particular when a user requests a search returning no results. Dubsar will redirect to the previous screen (if the search was performed using the search form), open the correct accordion pane and position it where it was when that pane was opened. This does not work in the general case of going back to a previous screen.
- Back: getting the display theme right If you navigate from one Dubsar screen to another, change the display theme, then immediately go back, the previous page will be displayed in the previous theme.
See Supported Browsers and Devices for updated information.
Dubsar requires a JavaScript-enabled browser. Currently, Dubsar works well in the following browsers:
- Firefox 3 on all platforms (Ubuntu, Vista, OS X)
- Google Chrome 6 & 7 on all platforms
- Safari 5 on OS X and Vista
- Camino 2 on OS X
- OmniWeb 5 on OS X
- Internet Explorer 8 on Vista
Dubsar has not been tested with a version of Internet Explorer below 8.
Dubsar works on the following browsers, but with significant styling glitches:
- Opera 10 on all platforms
- Konqueror 4 on Ubuntu Linux
The QUnit test suite currently passes in all listed browsers (except that the autocompleter tests are known to fail in Camino, Opera and Konqueror since the introduction of jquery-mockjax).
The server has been tested both on Ubuntu and OS X.