In 1.3.6 we focused on stability, without adding many features. These are the changes introduced between 1.3.5 and 1.3.7
- CSS Animations
Add CSS animations, like slide, fade, pop and flip, using the utility aria.utils.css.Animations
- Error tool tip enhancement
Currently the logic for the error tool tip is contained within aria.widgets.form.Input, the aim of this enhancement is to share code efficiently between multiple types of widgets. Specifically for the requirement of this feature, this means making the code for the error tool tip not only available for "Input" type widgets, but also for "Action" type widgets. In addition, it must also be possible from within a template to have a new widget property called errorTipPosition that will be used as the preferred position for the error tool tip, if there is not enough available space the framework will automatically calculate the best position for the error tool tip. The property will be added for both "Input" type widgets and also "Action" type widgets.
- improve ModuleCtrlTestCase
Improve ModuleCtrlTestCase by providing automatic creation and disposal of tested module. By specifying
$controllerin the test’s
$prototypean instance of that class is generated before running the test. The tester can then access the two variables
$moduleCtrlPrivate. The public interface is also registered for asserting its logs, so there’s no need to call anymore
- Using atpackager
- improve logging in tests
- Added Assert.assertEqualsWithTolerance(num1, num2, tolerance)
- Formatted output in Assert.assertJsonEquals Instead of dumping minimal JSON strings in failed JSON comparison, pretty-print them.
- Log to browser console in JSUnit in verbose mode
Currently, the SilentArrayAppender is the appender used in our JSUnit. This means that things like $logError or $logWarn will not be displayed in Firebug console. However, the appender is changed from DefaultAppender in the middle of the execution, which results in some logs actually being available in the browser console, but the rest (after changing appender) not. For debugging purposes, it’s useful to see the errors and warnings directly in the browser when running the test. This commit adds the possibility to see all the logs if the URL of the test page contains ‘verbose=true’ part.
Support more gestures: double tap, single tap, long press, drag, pinch.
- Utility class to load standard css files
It is possible to programmatically add/remove css files by using the aria.utils.CSSLoader singleton. Tags of type "link" are created and appended to the head of the document.
- Better stack traces in Firebug and Safari dev tools
Now almost all the functions (both from core AT code and user template scripts / module controllers) will have names displayed in the stack traces in Firebug and Safari dev tools, using Function.displayName feature. Previously many of the functions were displayed as anonymous.