angular.js -

Age	Commit message (Collapse)	Author
2013-11-06	chore(docs): add -webkit-transition for ngClass example	Matias Niemelä

2013-11-06	docs(guide/overview): Refactor overview and mvc docs	Tobias Bosch
	Before, there we multiple overview docs: - guide/overview - guide/introduction - guide/dev_guide.mvc - guide/dev_guide.mvc.understanding_model - guide/dev_guide.mvc.understanding_view - guide/concepts Now we have: - guide/introduction: High level description of Angular with the key benefits but without code or any concrete concepts - guide/concepts: explains all important concepts with a simple example and contains deep links to the other parts of the guide. All the old information was moved into existing documents or deleted when they were duplicates.
2013-11-06	chore(docs): specify how ngClass deals with natural CSS transitions	Matias Niemelä

2013-11-06	fix(ngView): only run anchorScroll after animation is done	Jeff Cross

2013-11-06	fix(ngMock): throw more descriptive errors for $animate.flushNext()	Jeff Cross

2013-11-06	fix(ngInclude): only run anchorScroll after animation is done	Pete Bacon Darwin
	We need to wait until animations have added the content to the document before trying to `autoscroll` to anchors that may have been inserted. Fixes #4723
2013-11-06	fix($animate): only apply the fallback property if any transition animations ↵	Matias Niemelä
	are detected
2013-11-05	chore(docs): refactor/improve new CSS transition code in examples	Matias Niemelä

2013-11-05	chore(docs): update $animate and ngAnimate docs	Matias Niemelä

2013-11-05	feat($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-05	fix($animate): avoid hanging animations if the active CSS transition class ↵	Matias Niemelä
	is missing Closes #4732 Closes #4490
2013-11-05	fix($animate): ensure staggering animations understand multiple delay values	Matias Niemelä

2013-11-05	fix($animate): ensure the active class is not applied if cancelled during reflow	Matias Niemelä
	Closes #4699
2013-11-05	chore($sniffer): make msie variable public	Matias 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-04	docs(input): fix typo	Tim Graham
	Closes #4734
2013-11-04	docs($http): note that default $http headers can be overridden	Dmitry Kichenko
	Closes #4750
2013-11-04	docs($log): add the word "safely" to clarify	granteagon
	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-04	fix(ngModel): deregister from the form on scope not DOM destruction	Igor 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-04	fix(ngIf): destroy child scope when destroying DOM	Igor Minar

2013-11-04	style: remove ws	Igor Minar

2013-11-04	docs($parse): Fix typo	Jordan Klassen

2013-11-02	docs($location): update paramValue description for search()	Freek Wielstra
	search() supports an array for paramValue, but this is not described in the docs.
2013-10-31	fix(ngEventDirectives): parse expression only once during compile phase.	Tobias Bosch

2013-10-30	feat($parse): secure expressions by hiding "private" properties	Chirayu 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-30	chore($compile): remove special case for ngIf and ngRepeat	Brian Ford

2013-10-30	chore: move getBlockElements to Angular.js	Brian Ford

2013-10-30	fix(ngIf): ngIf removes elements dynamically added to it	Brian 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-30	docs($route): split over-length line	Pete Bacon Darwin

2013-10-30	docs($route): change example module name	Andrew 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-28	fix($animate): use direct DOM comparison when checking for $rootElement	Matias Niemelä
	Closes #4679
2013-10-28	fix($animate): ensure former nodes are fully cleaned up when a follow-up ↵	Matias Niemelä
	structural animation takes place Closes #4435
2013-10-28	docs($provide): fix link to factory section	Pete Bacon Darwin

2013-10-28	fix($animate): ensure enable/disable animations work when the document node ↵	Matias Niemelä
	is used Closes #4669
2013-10-28	feat(ngAnimate): provide support for staggering animations with CSS	Matias Niemelä

2013-10-28	fix(angular-mocks): add inline dependency annotation	Derek Hammer
	Annotation allows the angular-mocks to be minified, which sometimes happens with frameworks that automatically process files before running tests. Also, some developers have been using this library in code for their applications. This is not recommended as the library is only designed to support testing and not production applications. If you are likely to want to use the code here in production you would be best forking and maintaining your own version of the code as we will not guarantee that we won't break the annotation of the code in the future. Closes #4448
2013-10-28	fix($compile): don't instantiate controllers twice for element transclude ↵	Igor Minar
	directives This is a fix for regression introduced last week by faf5b980. Closes #4654
2013-10-27	docs($resource): fix typo	Jarrett Harris
	Closes #4670
2013-10-27	docs(form): fix typo	Yuriy Bilogub
	Close #4671
2013-10-26	docs($location): document $location's events	Valentyn Shybanov
	Closes #1569 Closes #4446
2013-10-26	docs($q): promises are no longer automatically unwrapped, by default	rjferguson21
	Although it is still possible to turn this on, the feature is deprecated and it is best to remove this mention completely here. Closes #4632
2013-10-26	docs(Angular.js): angular.equals calls itself recursively on objects	thorn0
	Closes #4622
2013-10-26	docs(http): add missing brace in the 2nd interceptors example	mgechev
	Closes #4621
2013-10-26	docs(ngForm): ensure correct attribute name in usage example	David Bennett
	Closes #4611
2013-10-25	docs($rootScope): added $eval `locals` parameter documentation	Caio Cunha
	Added documentation for `locals` parameter of `$eval` method.
2013-10-25	fix($compile): attribute bindings should not break due to terminal directives	Igor Minar
	Recently we changed the priority of attribute interpolation directive to -100 to ensure that it executes early in the post linking phase. This causes issues with when terminal directives are placed on elements with attribute bindings because the terminal directive will usually have 0 or higher priority which results in attr interpolation directive not being applied to the element. To fix this issue I'm switching the priority back to 100 and making moving the binding setup into the pre-linking function. This means that: - terminal directives with priority lower than 100 will not affect the attribute binding - if a directive wants to add or alter bindings it can do so in the pre-linking phase, as long as the priority of this directive is more than 100 - all post-linking functions will execute after the attribute binding has been set up - all pre-linking functions with directive priority lower than 100 will execute after the attribute bindings have been setup BREAKING CHANGE: the attribute interpolation (binding) executes as a directive with priority 100 and the binding is set up in the pre-linking phase. It used to be that the priority was -100 in rc.2 (100 before rc.2) and that the binding was setup in the post-linking phase. Closes #4525 Closes #4528 Closes #4649
2013-10-25	docs(compile): fix typo in 'Attributes' description	BrainCrumbz
	Closes #4589
2013-10-25	docs(ngIf): fix typo	Balázs Suhajda
	Closes #4512
2013-10-24	docs(ngClass): fix typo	Sam Dornan
	Closes #4471
2013-10-24	docs(rootScope): add example of using a listener function for $watch	Wesley Cho
	Closes #4451
2013-10-24	style($route): fix line length	Pete Bacon Darwin