aboutsummaryrefslogtreecommitdiffstats
path: root/src
AgeCommit message (Collapse)Author
2013-10-26docs($location): document $location's eventsValentyn Shybanov
Closes #1569 Closes #4446
2013-10-26docs($q): promises are no longer automatically unwrapped, by defaultrjferguson21
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-26docs(Angular.js): angular.equals calls itself recursively on objectsthorn0
Closes #4622
2013-10-26docs(http): add missing brace in the 2nd interceptors examplemgechev
Closes #4621
2013-10-26docs(ngForm): ensure correct attribute name in usage exampleDavid Bennett
Closes #4611
2013-10-25docs($rootScope): added $eval `locals` parameter documentationCaio Cunha
Added documentation for `locals` parameter of `$eval` method.
2013-10-25fix($compile): attribute bindings should not break due to terminal directivesIgor 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-25docs(compile): fix typo in 'Attributes' descriptionBrainCrumbz
Closes #4589
2013-10-25docs(ngIf): fix typoBalázs Suhajda
Closes #4512
2013-10-24docs(ngClass): fix typoSam Dornan
Closes #4471
2013-10-24docs(rootScope): add example of using a listener function for $watchWesley Cho
Closes #4451
2013-10-24style($route): fix line lengthPete Bacon Darwin
2013-10-24fix($animate): skip unnecessary addClass/removeClass animationsMatias Niemelä
Skip addClass animations if the element already contains the class that is being added to element. Also skip removeClass animations if the element does not contain the class that is being removed. Closes #4401 Closes #2332
2013-10-24docs(ngModelController): $parent can help isolate scope directivesbasarat
2013-10-24docs($routeProvider): document route.resolve rejectionJosh Schumacher
Add documentation that the $routeChangeError event is fired when a route resolve promise is rejected Closes #4447
2013-10-24docs(select): fix typowiebl
Closes #4433
2013-10-24docs(ngBindHtml): add exampleNicolas Brugneaux
Closes #4427
2013-10-24fix($compile): instantiate controlers when re-entering compilationIgor 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-24docs(ngNonBindable): fix punctuationDave Peticolas
Closes #4424
2013-10-24docs($provide): Fix typoPete Bacon Darwin
Closes #4420
2013-10-24docs(ngController): do not attach a controller twiceTyler 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-24fix(input): keep track of min/max attars on-the-flyDmitry Shirokov
Now input[type=button] keeps track of both min and max attrs even if they change over time.
2013-10-23chore(docs): fix jsHint errors with long linesMatias Niemelä
2013-10-23docs(guide/directive,guide/compiler,): drastically improveBrian Ford
2013-10-23chore(ngMocks): shorten the length of the description line to avoid jsHint ↵Matias Niemelä
errors
2013-10-23feat(docs): provide index pages for each angular moduleMatias Niemelä
2013-10-23fix(ngView): ensure the new view element is placed after the old view elementMatias Niemelä
Closes #4362
2013-10-23fix($animate): ensure animations work properly when the $rootElement is ↵Matias Niemelä
being animated Closes #4397 Closes #4231
2013-10-23fix($animate): only cancel class-based animations if the follow-up class ↵Matias Niemelä
contains CSS transition/keyframe animation code Closes #4463 Closes #3784
2013-10-22style: make jshint happyVojta Jina
2013-10-22chore(grunt): add jshint tasksPete Bacon Darwin
2013-10-22fix: don't inline css in csp mode.tigbro
Also add `angular-csp.css` to the resulting build.
2013-10-22fix(ngAnimate): fix cancelChildAnimations throwing exceptionGrzegorz Lachowski
fix ngAnimate throwing exception in cancelChildAnimations on deletion of element (ngAnimate's leave decorator) of repeated element when using ng-include on this element. Closes #4548
2013-10-21docs(ngCsp): pretty-format docsIgor Minar
2013-10-18fix(csp): fix csp auto-detection and stylesheet injectionIgor 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-18docs: correct broken linksVojta Jina
This also contains some whitespace corrections by my editor.
2013-10-18fix($injector): allow a constructor function to return a functionVojta Jina
This change makes `$injector.instantiate` (and thus `$provide.service`) to behave the same as native `new` operator.
2013-10-15docs($rootScope): better document infinite digest and ttlIgor Minar
2013-10-15fix($parse): check function call context to be safeChirayu Krishnappa
Closes #4417
2013-10-14docs: add missing priority documentation for structural directivesIgor Minar
2013-10-14docs(ngInit): fix typoTyler McGinnis
Closes #4384
2013-10-14docs(ngNonBindable): improve descriptionPete Bacon Darwin
Closes #4391
2013-10-14docs(booleanAttrs): improve grammar and clarityDave Peticolas
Closes #4392
2013-10-12fix($animate): ensure that a timeStamp is created if not provided by the ↵Matias Niemelä
browser event Firefox and (sometimes) Opera may not provide a timeStamp value in their event when passed to the event handler. This may cause animations not to close properly. This fix will automatically create a timeStamp value for the event in this situation when missing. Closes #3053
2013-10-11fix($compile): abort compilation when duplicate element transclusionIgor Minar
Issue an error and abort compilation when two directives that ask for transclusion are found on a single element. This configuration is not supported and we previously failed to issue the error because in the case of element transclusion the compilation is re-started and this caused the compilation context to be lost. The ngRepeat directive has been special-cased to bypass this warning because it knows how to handle this scenario internally. This is not an ideal solution to the problem of multiple transclusions per element, we are hoping to have this configuration supported by the compiler in the future. See #4357. Closes #3893 Closes #4217 Closes #3307
2013-10-11fix(directives): correct priority of structural directivesIgor 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-11fix($compile): make order directives w/ same priority deterministicIgor Minar
Array.prototype.sort is speced out to be as potentionally unstable sort, which is how it's implemented in FF and IE. This has caused the order of directives with the same priority to vary between browsers. For consistency sake, we now consider directive name and registration, order when determining the order of directives with the same priority. Note: it is still possible to get into a situation when the directive order is underministic - when source files are loaded asynchronously in non-deterministic order and there are are directives registered with the same name and priority, the order in which they will be applied will depend on the file load order.
2013-10-11style: strip white space from filesIgor Minar
2013-10-11chore($compile): remove dead codeIgor Minar
2013-10-11docs(ngAnimate): fix typosHack Reactor Students
Closes #4375
generated by cgit v1.2.3 (git 2.25.1) at 2025-11-05 00:52:59 +0000