angular.js -

Age	Commit message (Collapse)	Author
2013-11-04	style: remove ws	Igor Minar

2013-10-31	fix(ngEventDirectives): parse expression only once during compile phase.	Tobias Bosch

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-27	docs(form): fix typo	Yuriy Bilogub
	Close #4671
2013-10-26	docs(ngForm): ensure correct attribute name in usage example	David Bennett
	Closes #4611
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(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	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-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.
2013-10-18	docs: correct broken links	Vojta Jina
	This also contains some whitespace corrections by my editor.
2013-10-14	docs: add missing priority documentation for structural directives	Igor Minar

2013-10-14	docs(ngInit): fix typo	Tyler McGinnis
	Closes #4384
2013-10-14	docs(ngNonBindable): improve description	Pete Bacon Darwin
	Closes #4391
2013-10-14	docs(booleanAttrs): improve grammar and clarity	Dave Peticolas
	Closes #4392
2013-10-11	fix(directives): correct priority of structural directives	Igor Minar
	BREAKING CHANGE: the priority of ngRepeat, ngSwitchWhen, ngIf, ngInclude and ngView has changed. This could affect directives that explicitly specify their priority. In order to make ngRepeat, ngSwitchWhen, ngIf, ngInclude and ngView work together in all common scenarios their directives are being adjusted to achieve the following precendence: Directive \| Old Priority \| New Priority ============================================= ngRepeat \| 1000 \| 1000 --------------------------------------------- ngSwitchWhen \| 500 \| 800 --------------------------------------------- ngIf \| 1000 \| 600 --------------------------------------------- ngInclude/ngView \| 1000 \| 400
2013-10-11	style: strip white space from files	Igor Minar

2013-10-10	docs(ngInit): add note on best practices	Brian Ford

2013-10-09	feat(ngRepeat): use block separator comments	jankuca
	Issue: multi-elements ng-repeat (ng-repeat-start, ng-repeat-end) can contain elements with a trancluding directive. This directive changes content of the row (template) and ng-repeat does not work correctly (when removing/moving rows), because ng-repeat works with the original template (elements). This changes ng-repeat behavior to traverse the DOM to find current elements everytime we are moving/removing rows (if the template has multiple elements). Closes #3104
2013-10-07	fix(input): `false` is no longer an empty value by default	Pete Bacon Darwin
	`checkboxInputType` and `ngList` directives need to have special logic for whether they are empty or not. Previously this had been hard coded into their own directives or the `ngRequired` directive. This made it difficult to handle these special cases. This change factors out the question of whether an input is empty into a method `$isEmpty` on the `ngModelController`. The `ngRequired` directive now uses this method when testing for validity and directives, such as `checkbox` or `ngList` can override it to apply logic specific to their needs. Closes #3490, #3658, #2594
2013-10-07	fix(*): protect calls to hasOwnProperty in public API	Peter Bacon Darwin
	Objects received from outside AngularJS may have had their `hasOwnProperty` method overridden with something else. In cases where we can do this without incurring a performance penalty we call directly on Object.prototype.hasOwnProperty to ensure that we use the correct method. Also, we have some internal hash objects, where the keys for the map are provided from outside AngularJS. In such cases we either prevent `hasOwnProperty` from being used as a key or provide some other way of preventing our objects from having their `hasOwnProperty` overridden. BREAKING CHANGE: Inputs with name equal to "hasOwnProperty" are not allowed inside form or ngForm directives. Before, inputs whose name was "hasOwnProperty" were quietly ignored and not added to the scope. Now a badname exception is thrown. Using "hasOwnProperty" for an input name would be very unusual and bad practice. Either do not include such an input in a `form` or `ngForm` directive or change the name of the input. Closes #3331
2013-10-07	style(select): fix semicolons and vars	Peter Bacon Darwin

2013-10-07	docs(ngModel): fix grammar and improve clarity	Dave Peticolas
	Closes #4291
2013-10-07	docs(ngValue): add docs for ngValue directive	Brian Ford
	Closes #4267
2013-10-05	docs(a): change model.$save() into something less deceptive	Michiel Staessen
	Closes #4215
2013-10-05	docs(ngList): improve grammar and clarity	Dave Peticolas

2013-10-03	fix($compile): fix (reverse) directive postLink fn execution order	Igor Minar
	previously the compile/link fns executed in this order controlled via priority: - CompilePriorityHigh, CompilePriorityMedium, CompilePriorityLow - PreLinkPriorityHigh, PreLinkPriorityMedium, PreLinkPriorityLow - link children - PostLinkPriorityHigh, PostLinkPriorityMedium, PostLinkPriorityLow This was changed to: - CompilePriorityHigh, CompilePriorityMedium, CompilePriorityLow - PreLinkPriorityHigh, PreLinkPriorityMedium, PreLinkPriorityLow - link children - PostLinkPriorityLow, PostLinkPriorityMedium , PostLinkPriorityHigh Using this order the child transclusion directive that gets replaced onto the current element get executed correctly (see issue #3558), and more generally, the order of execution of post linking function makes more sense. The incorrect order was an oversight that has gone unnoticed for many suns and moons. (FYI: postLink functions are the default linking functions) BREAKING CHANGE: the order of postLink fn is now mirror opposite of the order in which corresponding preLinking and compile functions execute. Very few directives in practice rely on order of postLinking function (unlike on the order of compile functions), so in the rare case of this change affecting an existing directive, it might be necessary to convert it to a preLinking function or give it negative priority (look at the diff of this commit to see how an internal attribute interpolation directive was adjusted). Closes #3558
2013-10-03	docs(ngInclude): clarity, formatting	Dave Peticolas
	Closes #4222
2013-10-03	docs(ngClass): clarify the description	Dave Peticolas
	Closes #4220
2013-10-03	docs(select): clarify usage	gdennie
	The wording seemed confusing and these adjustments seem to capture the intent with less turbulence. Closes #4257
2013-10-01	refactor(select): simplify the ngOptions regular expression	Stefan hr Berder
	\w matches [a-zA-Z0-9_] and \d matches [0-9], using both in a character set is simply redundant. Closes #3903
2013-09-30	fix(ngTransclude): detect ngTranslude usage without a transclusion directive	jankuca
	Closes #3759
2013-09-27	docs(ngIf): formatting, clarity	Dave Peticolas

2013-09-27	docs(ngController): fix grammar	Dave Peticolas

2013-09-27	docs(ngCsp): fix grammar	Dave Peticolas

2013-09-27	docs(dblClick): fix grammar	Dave Peticolas

2013-09-27	docs(ngDisabled): clarify	Dave Peticolas

2013-09-26	feat(ngEventDirectives): add `ngCopy`, `ngCut`, and `ngPaste`	Ben McCann
	Closes #4172, #4170
2013-09-25	docs(ngHref): fix formatting and clarify	Dave Peticolas
	Closes #4106
2013-09-25	docs(ngShowHide): improve clarity	Dave Peticolas
	Closes #4099
2013-09-25	fix(ngRepeat): correctly track elements even when the collection is ↵	jankuca
	initially undefined Previously if the collection model was set to undefined on the first digest, the repeater would get confused and not use the correct tracking function for associating model with dom elements in the repeater. Closes #4145 Closes #3964