-
Notifications
You must be signed in to change notification settings - Fork 0
Release Notes 1.0.2
jdee edited this page Jul 1, 2011
·
5 revisions
Release 1.0.2 of Dubsar adds some missing content and fixes several bugs. In addition, this release provides some integration with social networks as well as an RSS feed.
December 6, 2010
- Added social links Dubsar now has links to social networks in the header.
- Added OpenGraph tags for Facebook The Dubsar index view now has OpenGraph tags to place it properly in the Facebook graph.
- Added an RSS feed Dubsar now provides an RSS feed of the updates in the news pane.
- Invalid inflections Issue 8 Hurt was incorrectly conjugated hurted. That invalid inflection has been removed.
- Autocompleter tests fails in Camino Issue 19 Dubsar did not update its jquery-mockjax plug-in or jQuery/jQuery UI. But the failure disappeared. It may have been solved by browser updates.
- Search form does not ignore trailing white space Issue 20 Dubsar would return no results if a trailing white space were accidentally included in a search term.
- Google Chrome on OS X sometimes hangs Issue 21 This was observed a number of times right after the last release, but has not been seen for some time now.
- Missing sample sentences Issue 23 The WordNet sample sentences from sents.vrb were accidentally omitted. They are now present among verb frames in the tooltips.
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.
- 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.
- Header bar doesn't display well in a narrow window If the window is made too narrow, the search form will overlap the alphabet links on the left of the header bar.
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 & 8 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.
The server has been tested both on Ubuntu and OS X.