bower-angular-scenario
This tool is now in maintenance mode. If you are starting a new project, please use
Protractor. Existing projects using scenario runner are
advised to migrate to protractor, as this tool is unlikely to receive updates.
This repo is for distribution on bower
. The source for this module is in the
main AngularJS repo.
Please file issues and pull requests against that repo.
Install
Install with bower
:
bower install angular-scenario
Documentation
Documentation is available on the
AngularJS docs site.
License
The MIT License
Copyright (c) 2010-2012 Google, Inc. http://angularjs.org
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
1.3.0-rc.5 impossible-choreography (2014-10-08)
Bug Fixes
- $anchorScroll: don't scroll to top when initializing and location hash is empty
(d5445c60,
#8848, #9393)
- $animate:
- ensure hidden elements with ngShow/ngHide stay hidden during animations
(39d0b368,
#9103, #9493)
- permit class-based animations for leave operations if ngAnimateChildren is enabled
(df1a00b1,
#8092, #9491)
- ensure that class-based animations only consider the most recent DOM operations
(c93924ed,
#8946, #9458)
- abort class-based animations if the element is removed during digest
(613d0a32,
#8796)
- clear the GCS cache even when no animation is detected
(cb85cbce,
#8813)
- $browser:
- $compile:
- $http: honor application/json response header and parse json primitives
(7b6c1d08,
#2973)
- $injector: throw when factory $get method does not return a value
(0d3b69a5,
#4575, #9210)
- $location: allow
0
in path()
and hash()
(b8c5b871) - form: fix submit prevention
(86c7d122,
#3370, #3776)
- ngAnimate: defer DOM operations for changing classes to postDigest
(667183a8,
#8234, #9263)
- orderBy: sort by identity if no predicate is given
(607f016a,
#5847, #4579, #9403)
- select:
Features
Performance Improvements
- $animate:
- access DOM less in resolveElementClasses
(22358cf9)
- don't join classes before it's necessary in resolveElementClasses
(003c44ec)
- ngBind: set textContent rather than using element.text()
(074a146d,
#9369, #9396)
Breaking Changes
If a template contains directives within comment nodes, and there is more than a single node in the
template, those comment nodes are removed. The impact of this breaking change is expected to be
quite low.
Closes #9212
Closes #9215
The $animate
CSS class API will always defer changes until the end of the next digest. This allows ngAnimate
to coalesce class changes which occur over a short period of time into 1 or 2 DOM writes, rather than
many. This prevents jank in browsers such as IE, and is generally a good thing.
If you find that your classes are not being immediately applied, be sure to invoke $digest()
.
Closes #8234
Closes #9263
ngOptions
will now throw an error when the comprehension expressions contains both a select as
and track by
expression.
These expressions are fundamentally incompatible because it is not possible to reliably and
consistently determine the parent object of a model, since select as
can assign any child of a
value
as the model value.
Prior to refactorings in this release, neither of these expressions worked correctly independently,
and did not work at all when combined.
See #6564
Order of events has changed.
Previously: $locationChangeStart
-> $locationChangeSuccess
-> $routeChangeStart
-> $routeChangeSuccess
Now: $locationChangeStart
-> $routeChangeStart
-> $locationChangeSuccess
-> -> $routeChangeSuccess
Fixes #5581
Closes #5714
Closes #9502
<a name="1.3.0-rc.4"></a>