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.
…ementation. The problem is that this is still a change of another nature compared to the others: we remove it, but we have another property which is not quite equivalent but can be used as replacement. Concretely, `environment` was considered as a synonym of `osName`, and corresponded to the latter's value. This should not be the case, but the documentation and the deprecation logging should reflect the alternative. A custom message could be added to the definition of deprecated properties. Closes #1421
…ity for Orientation class. This commit can be reverted as soon as the deprecation period has ended. It completes commit 608c176 and the latter should be considered regarding the date of the deprecation.
…d Orientation class. There is another commit dealing with the deletion of deprecated code, but this one completes it by removing some code which has been missed.
It is now possible for a user to customize the error messages used by the widgets. There are 3 levels of error messages specifications, the two firsts being user configuration while the last is the hardcoded default. This is resolved in this order of precedence: - local: widget's configuration - global: application's environment - hardcoded: widget's resources