aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
2013-11-06fix($animate): only apply the fallback property if any transition animations ↵Matias Niemelä
are detected
2013-11-05chore(docs): refactor/improve new CSS transition code in examplesMatias Niemelä
2013-11-05chore(docs): update $animate and ngAnimate docsMatias Niemelä
2013-11-05feat($animate): ensure CSS transitions can work with inherited CSS class ↵Matias Niemelä
definitions BREAKING CHANGE ngAnimate addClass / removeClass animations are now applied right away. This means that as soon as the animation starts the class will be added (addClass) or removed (removeClass) to the element being animated instead of after the -add-active / -remove-active animations are completed. This allows for animations outside of ngAnimate to not conflict with $animate. This commit introduces beforeAddClass and beforeRemoveClass animation event functions and executes any addClass and removeClass event functions AFTER the class has been added or removed (this is opposite functionality of how ngAnimate used to work when performing JS-enabled animations addClass / removeClass animations). If your animation code relies on any animations being performed prior to the class change then simply use the new beforeAddClass and beforeRemoveClass animation event functions. Finally, when animating show and hide animations using CSS transitions or keyframe animations, ng-hide-remove doesn't require `display:block!important` for ng-hide-add anymore.
2013-11-05chore(animateSpec): provide meaningful CSS class names in animation testsMatias Niemelä
2013-11-05fix($animate): avoid hanging animations if the active CSS transition class ↵Matias Niemelä
is missing Closes #4732 Closes #4490
2013-11-05fix($animate): ensure staggering animations understand multiple delay valuesMatias Niemelä
2013-11-05fix($animate): ensure the active class is not applied if cancelled during reflowMatias Niemelä
Closes #4699
2013-11-05chore($sniffer): make msie variable publicMatias Niemelä
The msie variable is a global variable used within the ng core which contains the version number for the current Internet Explorer browser that is rendering the application. Other modules outside of the ng core could make use of this variable instead of having to rollout duplicate detection code. This code makes it easy to reuse this simple property within the $sniffer service.
2013-11-05chore(ngAnimate): ensure elapsedTime values are in seconds and millsecondsMatias Niemelä
2013-11-05chore(grunt): add test:docsgen to ci checksPete Bacon Darwin
2013-11-05fix(ngdocs): create mock Doc objects correctlyPete Bacon Darwin
2013-11-05fix(ngdocs): `shortDescription()` should not error if no `description`Pete Bacon Darwin
2013-11-05docs(guide/directive): fix transclusion exampleMichal Bendowski
The example about transclusion and scopes worked only because the order of `scope` and `element` arguments is wrong, which means that the `name' property of the scope is not really being updated. To really work, the directive has to define its own scope, either a new child scope or, as is more common with transclusion, an isolated scope. Closes #4774
2013-11-04docs(guide): add SEO4Ajax to the SEO tools listG Lormeau
Closes #4748
2013-11-04docs(input): fix typoTim Graham
Closes #4734
2013-11-04docs($http): note that default $http headers can be overriddenDmitry Kichenko
Closes #4750
2013-11-04docs(guide/understanding-controllers): fix typo in examplejoshbowdoin
Broken - $scope.spicy = 'very'; Works - $scope.spice = 'very'; Closes #4752
2013-11-04docs(overview): improve readabilityJesse Palmer
Inserted a couple of line breaks to increase readability. Closes #4756
2013-11-04docs($log): add the word "safely" to clarifygranteagon
I was reading the doc and had to read the code to be sure it was safe. Spelling it out seems easier. Closes #4760
2013-11-04chore(docs): fix ordering of docs in the guideBrian Ford
2013-11-04fix(ngModel): deregister from the form on scope not DOM destructionIgor Minar
Due to animations, DOM might get destroyed much later than scope and so the element $destroy event might get fired outside of $digest, which causes changes to the validation model go unobserved until the next digest. By deregistering on scope event, the deregistration always happens in $digest and the form validation model changes will be observed. Closes #4226 Closes #4779
2013-11-04fix(ngIf): destroy child scope when destroying DOMIgor Minar
2013-11-04style: remove wsIgor Minar
2013-11-04docs(guide/contribute): remove redundancy and link to CONTRIBUTING.mdBrian Ford
2013-11-04docs($parse): Fix typoJordan Klassen
2013-11-02docs($location): update paramValue description for search()Freek Wielstra
search() supports an array for paramValue, but this is not described in the docs.
2013-10-31fix(ngEventDirectives): parse expression only once during compile phase.Tobias Bosch
2013-10-30feat($parse): secure expressions by hiding "private" propertiesChirayu Krishnappa
BREAKING CHANGE: This commit introduces the notion of "private" properties (properties whose names begin and/or end with an underscore) on the scope chain. These properties will not be available to Angular expressions (i.e. {{ }} interpolation in templates and strings passed to `$parse`) They are freely available to JavaScript code (as before). Motivation ---------- Angular expressions execute in a limited context.  They do not have direct access to the global scope, Window, Document or the Function constructor.  However, they have direct access to names/properties on the scope chain.  It has been a long standing best practice to keep sensitive APIs outside of the scope chain (in a closure or your controller.)  That's easier said that done for two reasons: (1) JavaScript does not have a notion of private properties so if you need someone on the scope chain for JavaScript use, you also expose it to Angular expressions, and (2) the new "controller as" syntax that's now in increased usage exposes the entire controller on the scope chain greatly increaing the exposed surface.  Though Angular expressions are written and controlled by the developer, they (1) typically deal with user input and (2) don't get the kind of test coverage that JavaScript code would.  This commit provides a way, via a naming convention, to allow publishing/restricting properties from controllers/scopes to Angular expressions enabling one to only expose those properties that are actually needed by the expressions.
2013-10-30chore($compile): remove special case for ngIf and ngRepeatBrian Ford
2013-10-30chore: move getBlockElements to Angular.jsBrian Ford
2013-10-30fix(ngIf): ngIf removes elements dynamically added to itBrian Ford
When using ngIf with ngInclude on the same element, ngIf previously did not remove elements added by ngInclude. Similarly, when using ngIfStart/End, ngIf will miss elements added between the start/end markers added after ngIf is linked. This commit changes the behavior of ngIf to add a comment node at the end of its elements such that elements between the starting comment and this ending comment are removed when ngIf's predicate does not hold.
2013-10-30feat(Angular.js): add externs file for Closure CompilerMartin Probst
This adds an (incomplete) externs file for use with the Closure Compiler. Users can pass this as -extern to the compiler pass to get type checking and protect their AngularJS use against property renaming in advanced compilation mode.
2013-10-30docs(api): fix broken linksPete Bacon Darwin
2013-10-30docs(api): fix broken linksFred Sauer
Closes #4705
2013-10-30docs(guide/injecting-services): fix indentation in exampleAdam Bowen
Closes #4714
2013-10-30docs($route): split over-length linePete Bacon Darwin
2013-10-30docs(tutorial): add instructions to install karma pluginsRenan Ivo
2013-10-30docs($route): change example module nameAndrew Jackson
The name of the example module is `ngView`, which might cause needless confusion. Changed name to `ngViewExample`, which should make it clearer. Closes #4702
2013-10-30docs(guide/e2e-testing): fix typoEl Juli
Closes #4700
2013-10-30docs(api): improve grammarJoeLeCodeur
Closes #4690
2013-10-30docs(CONTRIBUTING.md): add more info for contributorsPete Bacon Darwin
Closes #4636
2013-10-30docs(guide/understanding_controller): correct grammarandre
Add the word "to" to improve grammar. Closes #4698
2013-10-28fix($animate): use direct DOM comparison when checking for $rootElementMatias Niemelä
Closes #4679
2013-10-28fix($animate): ensure former nodes are fully cleaned up when a follow-up ↵Matias Niemelä
structural animation takes place Closes #4435
2013-10-28docs(guide/directive): fix myDraggable for zoomed pageGabor Csizmadia
If you have zoomed into the page in your browser then the screen coordinate system no longer matches the page coordinate system. To ensure that dragged elements work correctly when zoomed we should use pageX/pageY rather than screenX/screenY. Closes #4687
2013-10-28docs(guide): improve links to booksPete Bacon Darwin
Nested bullet points don't appear very nicely so resorted to nested heading for the Learning Resources and in particular Books sections. Closes #4677
2013-10-28docs(guide): add link to bookChristopher Hiller
2013-10-28docs($provide): fix link to factory sectionPete Bacon Darwin
2013-10-28fix($animate): ensure enable/disable animations work when the document node ↵Matias Niemelä
is used Closes #4669
generated by cgit v1.2.3 (git 2.25.1) at 2025-11-02 22:00:41 +0000