angular.js -

Age	Commit message (Collapse)	Author
2013-11-07	feat(jqLite): expose isolateScope() getter similar to scope()	Igor Minar
	See doc update in the diff for more info. BREAKING CHANGE: jqLite#scope() does not return the isolate scope on the element that triggered directive with isolate scope. Use jqLite#isolateScope() instead.
2013-11-07	fix($compile): don't leak isolate scope state when replaced directive is ↵	Igor Minar
	used multiple times When an isolate scope directive is also a "replace" directive and at the root of its template it has other directives, we need to keep track remember to use isolate scope when linking these. This commit fixes the leakage of this state when this directive is used again later inside or outside of the isolate directive template.
2013-11-07	fix($compile): correct isolate scope distribution to controllers	Igor Minar
	Fixes an issue when we didn't share the isolate scope with the controller of the directive from the isolate directive's template when this directive was replaced onto the isolate directive element.
2013-11-07	fix($compile): replaced element has isolate scope	Misko Hevery

2013-11-07	fix($compile): only pass isolate scope to children that belong to the ↵	Vojta Jina
	isolate directive I had to fix one unit test, as it assumed the broken behavior, where application template gets the isolate scope of other (isolate) directive, rather than the regular scope. BREAKING CHANGE: Child elements that are defined either in the application template or in some other directives template do not get the isolate scope. In theory, nobody should rely on this behavior, as it is very rare - in most cases the isolate directive has a template.
2013-11-07	fix($compile): make isolate scope truly isolate	Vojta Jina
	Fixes issue with isolate scope leaking all over the place into other directives on the same element. Isolate scope is now available only to the isolate directive that requested it and its template. A non-isolate directive should not get the isolate scope of an isolate directive on the same element, instead they will receive the original scope (which is the parent scope of the newly created isolate scope). Paired with Tobias. BREAKING CHANGE: Directives without isolate scope do not get the isolate scope from an isolate directive on the same element. If your code depends on this behavior (non-isolate directive needs to access state from within the isolate scope), change the isolate directive to use scope locals to pass these explicitly. // before <input ng-model="$parent.value" ng-isolate> .directive('ngIsolate', function() { return { scope: {}, template: '{{value}}' }; }); // after <input ng-model="value" ng-isolate> .directive('ngIsolate', function() { return { scope: {value: '=ngModel'}, template: '{{value}} }; }); Closes #1924 Closes #2500
2013-11-07	docs(guide/filter): Refactor filter guide docs	Tobias Bosch
	This refactors the filter guide docs into a single file. Also removes out of date references to the fact that Angular used to enhance Arrays while evaluating expressions.
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(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-05	chore(docs): refactor/improve new CSS transition code in examples	Matias Niemelä

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-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(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(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	docs(ngModelController): $parent can help isolate scope directives	basarat

2013-10-24	docs(select): fix typo	wiebl
	Closes #4433
2013-10-24	docs(ngBindHtml): add example	Nicolas Brugneaux
	Closes #4427
2013-10-24	fix($compile): instantiate controlers when re-entering compilation	Igor Minar
	When we re-enter compilation either due to async directive templates or element transclude directive we need to keep track of controllers to instantiate during linking. This piece of info was missing when re-entering compilation and that's what this commit fixes. I also reordered the properties in the previousCompileContext object. Closes #4434 Closes #4616
2013-10-24	docs(ngNonBindable): fix punctuation	Dave Peticolas
	Closes #4424
2013-10-24	docs(ngController): do not attach a controller twice	Tyler McGinnis
	A common mistake for beginners is to attach a controller in both the $routeProvider and also in the html document using the ng-controller directive. This change highlights this, to help prevent developers from doing so in the future. Closes #4409
2013-10-24	fix(input): keep track of min/max attars on-the-fly	Dmitry Shirokov
	Now input[type=button] keeps track of both min and max attrs even if they change over time.
2013-10-23	docs(guide/directive,guide/compiler,): drastically improve	Brian Ford

2013-10-22	style: make jshint happy	Vojta Jina

2013-10-22	fix: don't inline css in csp mode.	tigbro
	Also add `angular-csp.css` to the resulting build.
2013-10-21	docs(ngCsp): pretty-format docs	Igor Minar

2013-10-18	fix(csp): fix csp auto-detection and stylesheet injection	Igor Minar
	When we refactored , we broke the csp mode because the previous implementation relied on the fact that it was ok to lazy initialize the .csp property, this is not the case any more. Besides, we need to know about csp mode during bootstrap and avoid injecting the stylesheet when csp is active, so I refactored the code to fix both issues. PR #4411 will follow up on this commit and add more improvements. Closes #917 Closes #2963 Closes #4394 Closes #4444 BREAKING CHANGE: triggering ngCsp directive via `ng:csp` attribute is not supported any more. Please use data-ng-csp instead.