… icon This pull request fixes the following issue: when an @aria:MultiSelect widget is empty (i.e. when its items property is an empty array) and when clicking on the dropdown icon to open the popup, the widget gets the focused style and keeps it forever (even when the focus is somewhere else).
…n option Clicking on a multiselect option often triggers a refresh, which may lead to the multiselect being visually moved. This commit makes sure that, in that case, the popup moves along with the multiselect.
As /src/aria/core/useragent/ua-parser.js was ignored through a .gitignore file which had no corresponding .npmignore file, the .gitignore file was used as the default .npmignore, leading to /src/aria/core/useragent/ua-parser.js not being included in the npm package (which makes the yeoman generator "yo ariatemplates" fail, cf http://ariatemplates.com/forum/showthread.php?tid=267).
This commit improves the detection of attester to not apply the offset when not needed.
This commit improves the detection of the extra pixels returned by getBoundingClientRect in IE 7.
In IE 7 and 8, aria.utils.Dom.getStyle(domElt, "borderTopWidth") can return something like "medium", which was unexpected by the aria.utils.overlay.Overlay._setInPosition method, which would then fail with an "Invalid argument" exception (when setting "NaNpx" for the width or height property of the overlay style). After 604f33b, now that an Overlay is created by default for movable dialogs, this problem made several movable dialog tests fail in IE 7 and IE 8, such as: test.aria.widgets.container.dialog.movable.test1.MovableDialogTestCase test.aria.widgets.container.dialog.movable.test2.MovableDialogTestCaseTwo test.aria.widgets.container.dialog.movable.test3.MovableDialogTestCaseThree test.aria.widgets.container.dialog.movable.test4.MovableDialogTestCaseFour test.aria.widgets.container.dialog.movable.test5.MovableDialogTestCaseFive test.aria.widgets.container.dialog.movable.issue367.MovableDialogTestCase This commit fixes the issue about the unexpected value, which fixes the above tests.
atLoader is used to synchronously load Aria Templates classes that are not included in the AT package. It is sufficient to insert the array of classes as the innerHTML of the tag used to load this script. All the classes' dependencies have to be added to this array. No comments or other sintax is allowed in it except for the array itself. close #1454
When two `html:RadioButton`s disabled state is bound to the same non-initialized data model, an error was triggered. This was due to the fact that when the `initWidget` method of the first one was called, a `setValue` was done on the data model, which triggered some listeners to modify the disabled state of the second one, for which the `initWidget` method had not been called yet, so that property `this._domElt` had not been set yet.
…s are identical If you inject an object into another setting the merge flag to true, if the objects are identical and contain cyclic references, then the maximum call stack size is exceeded.
any pattern Refactor of aria.utils.Date._interpretAgainstPattern
… be loaded Fixes test.aria.templates.reloadResources.ReloadResourcesTestCase which fails when using the new syntax (with "require") in compiled templates (as changed in the previous commit).
This commit changes the format in which Aria Templates is packaged. Instead of using the previous ATMultipart format (which does not allow packages to be evaluated in a script tag), it is now using the ATFillCache format (which fills the cache when packages are directly evaluated in a script tag). close #1415
…nce each time validateModel is called. close #1449
method is called
… to Date.format
This commit introduces a check on the status of the widget before reacting to data change. It can happen that the `_notifyDataChange` method is called after the widget destruction.
This commit adds the possibility to load in the Classic Test Runner the extrascripts exposed in attester's config, when CTR is run in isolated mode. Previously, the extrascripts were injected by attester only to CTR's index page, but CTR had no possibility to propagate those scripts into the iframe when tests were run with `#runIsolated=true` in the URL. This commit needs attester/attester#121 integrated in attester (to be released in attester 2.2.0) in order for it to properly expose `before` and `after` extrascripts. Close #1411
Added backward compatibility for widget's default error messages customization. The non-backward change concerns the keys used inside a resource file to define the hardcoded fallback for default values. There is no deprecation message or so on because the broken feature was not a public feature, but a commonly agreed hack.
The implementation and tests code is now cleaner, and the tests are more documented. A little bit of redundancy checking has been introduced in the tests just to make sure that if the order of some methods changes or if some are removed or whatever the tests will still work and be comprehensive. Also fixed a small mistake in AutoComplete's default error messages test. An unwanted `return` statement was remaining at the end of the `$constructor` of the test. It was not breaking anything regarding our class system implementation, but this remains incorrect.