aboutsummaryrefslogtreecommitdiffstats
path: root/src
AgeCommit message (Collapse)Author
2013-11-21fix($resource): Always return a resource instance when calling class methods ↵Tobias Bosch
on resources. Previously, calling `MyResource.save(myResourceInstance)`returned a promise, in contrast to the docs for `$resource`. However, calling `MyResource.save({name: 'Tobias"})`already correctly returned a resource instance. Fixes #4545. Closes #5061.
2013-11-21feat(input): hold listener during text compositionChia-liang Kao
When composing text in CJKV, intermediate buffer for unfinished text should not be updating the bound scope variables. Closes #4684
2013-11-20fix(ngAnimate): use a fallback CSS property that doesn't break existing stylesMatias Niemelä
The clip property seems to remove the box-shadow property when an absolute positioned animation is ongoing. This fix changes the property to be border-spacing which is also very underused. The border-spacing CSS property is only visible when border-collapse is set to separate. Closes #4902 Closes #5030
2013-11-20refactor($sce): Use $sniffer instead of $document for feature detection.Tobias Bosch
Also adds `$sniffer.msieDocumentMode` property. Closes #4931 Closes #5045
2013-11-20fix(ngClass): ensure that ngClass only adds/removes the changed classesMatias Niemelä
ngClass works by removing all the former classes and then adding all the new classes to the element during each watch change operation. This may cause transition animations to never render. The ngClass directive will now only add and remove the classes that change during each watch operation. Closes #4960 Closes #4944
2013-11-20fix($animate): ensure the DOM operation isn't run twiceMatias Niemelä
Depending on the animations placed on ngClass, the DOM operation may run twice causing a race condition between addClass and removeClass. Depending on what classes are removed and added via $compile this may cause all CSS classes to be removed accidentally from the element being animated. Closes #4949
2013-11-20fix(ngInclude): allow ngInclude to load scripts when jQuery is includedBrian Ford
In 1.2, the behavior of ngInclude was modified to use DOM APIs rather than jqLite. This means that even when jQuery was loaded, ngInclude was not calling into it, and thus scripts were not eval'd as they had been before. Although the use of ngInclude to eval scripts as a lazy-loading strategy was never an intentional feature, this patch restores the ability to do so. Closes #3756
2013-11-20docs($log): the documented default log behavior was incorrectMichel Salib
Closes #4953
2013-11-20docs(ngAnimate): fixed two small typosJarrett Harris
Line 162: 'defiend' should be 'defined' Line 225: 'callback function be excuted' should be 'callback function will be executed'. Closes #5048
2013-11-20docs(booleanAtts): explain the motivation for boolean attributesgdennie
It was not explicitly and consistently stated that the transient nature of boolean attributes precludes them from hosting binding expressions. This change make that more clear and reinforces the simplicity and elegance of the solution. Closes #5031
2013-11-20docs(ngRepeat): fix typoStéphane Reynaud
Replace "ian" in "in" Closes #5027
2013-11-20docs(ngPluralize): Fix missing space before parenthesesStéphane Reynaud
There should be a space between "braces" and "(`{}`)" Closes #5026
2013-11-20docs(api): example for $provide.value() uses $provide.value()jbnizet
The example code for `$provide.value()` actually used `$provide.constant()`. It now uses `$provide.value()`. Closes #4983 Closes #4990
2013-11-20docs(ngRoute): make it easier to find the examplePete Bacon Darwin
Closes #4975
2013-11-19docs($animate): update the docs explaining enable/disable for specific elementsMatias Niemelä
2013-11-18docs(ngApp): improve description and examplePete Bacon Darwin
2013-11-14docs(ngResource): removed buzz client exampleJeff Cross
The Buzz Client example on the ngResource doc was causing parse errors. While the root cause is being investigated, the example has been removed, and should be replaced by a more relevant example anyhow.
2013-11-14fix($compile): accessing controllers of transcluded directives from childrenTobias Bosch
Additional API (backwards compatible) - Injects `$transclude` (see directive controllers) as 5th argument to directive link functions. - `$transclude` takes an optional scope as first parameter that overrides the bound scope. Deprecations: - `transclude` parameter of directive compile functions (use the new parameter for link functions instead). Refactorings: - Don't use comment node to temporarily store controllers - `ngIf`, `ngRepeat`, ... now all use `$transclude` Closes #4935.
2013-11-14refactor($compile): move function def out of loopTobias Bosch
2013-11-14fix(loader): don't rely on internal APIsVojta Jina
This significantly increases the size of the loader: - minified: 1031bytes -> 1509bytes (+46%) - minified + gzip: 593bytes -> 810bytes (+36%) I'm not entirely sold on the idea of shipping minErr with the loade. With the current state, the angular-loader behavior is completely broken - this is just a quick fix, we can revisit this change in the future. Closes #4437 Closes #4874
2013-11-14fix(minErr): remove references to internals APIsVojta Jina
So that we can use minErr with angular-loader, before full angular is loaded. This also fixes replacing the version during the build.
2013-11-14chore(mocks): Remove reference to flushNextJames deBoer
Closes #4885
2013-11-14docs(ngClass): fix e2e test for examplePete Bacon Darwin
Broken by fd7bca22e16b0ecbe1feaf49bab39d9a44b8df01
2013-11-14docs(NgModelController): document `$viewChangeListeners` propertyCaitlin Potter
Closes #4948
2013-11-14docs(FormController): remove unnecessary parenthesisStéphane Reynaud
Closes #4936
2013-11-14docs(ngClass): distinguish between CSS classes and scope propertiesPete Bacon Darwin
Closes #4914
2013-11-14docs(NgModelController): clarify documentation of `$setViewValue`Mathis Hofer
$setViewValue does not really "Read a value from view". It should be called to trigger the ngModel to be updated when the value in the view changes. Closes #4907
2013-11-14docs($q): add missing closing parentheses in code examplersnapp
Closes #4900
2013-11-14docs(resource): fix grammatical issuemkolodny
'Case' should be the plural 'cases' since it is talking about multiple possible cases rather than a single case. For slightly more info, see the section 'When words like "none" are the subject' in this article: http://writing.wisc.edu/Handbook/SubjectVerb.html
2013-11-14docs(ngBindHtml): fix dependency for Plunker and JSFiddle in examplePete Bacon Darwin
The `<doc:example>` directive does not load up the dependencies correctly. Using the `<example>` directive, with `<file>` elements fixes this. Closes #4951
2013-11-13feat($parse): revert hiding "private" propertiesVojta Jina
Hiding `_*` properties was a feature primarily for developers using Closure compiler and Google JS style. We didn't realize how many people will be affected by this change. We might introduce this feature in the future, probably under a config option, but it needs more research and so I'm reverting the change for now. This reverts commit 3d6a89e8888b14ae5cb5640464e12b7811853c7e. Closes #4926 Closes #4842 Closes #4865 Closes #4859 Closes #4849 Conflicts: src/ng/parse.js
2013-11-13fix(urlUtils): made removal of windows drive from path saferJeff Cross
Prior to this fix, the urlResolve method would automatically strip the first segment of a path if the segment ends in a colon. This was to correct undesired behavior in the $location service using the file protocol on windows in multiple browsers (see #4680). However, there could be cases where users intentionally have first path segments that end in a colon (although this conflicts with section 3.3 of rfc3986). The solution to this problem is an extra check to make sure the first path segment of the input url does not end with a colon, to make sure we're only removing undesired path segments. Fixes #4939
2013-11-13docs($compile): Explain that post-link functions run in reverse order.Martin Field
Update the $compile docs to mention the change introduced in #4266. Closes #4843
2013-11-13docs($http): improve $http's caching documentationJulien Sanchez
Make the possibility to pass a custom cache instance to $http more obvious. Closes #4803
2013-11-12fix(urlUtils): urlUtils doesn't return right path for file:// on winROUL
Chrome and other browsers on Windows often append the drive name to the pathname, as described in #4680. This would cause the location service to browse to odd URLs, such as /C:/myfile.html, when opening apps using file://. Fixes #4680
2013-11-12fix($compile): correctly handle interpolated style in replace templatesTobias Bosch
A directive with a template with `replace: true` and an interpolated style at the root element should work correctly. Closes #4882.
2013-11-11fix(ngIf): don't create multiple elements when changing from a truthy to ↵Tobias Bosch
another thruthy value. Fixes #4852.
2013-11-11fix($resource): don't use $parse for @dotted.memberChirayu Krishnappa
params and paramDefaults support looking up the parameter value from the data object. The syntax for that is `@nested.property.name`. Currently, $resource uses $parse to do this. This is too liberal (you can use values like `@a=b` or `@a | filter` and have it work - which doesn't really make sense). It also puts up a dependency on $parse which is has restrictions to secure expressions used in templates. The value here, though a string, is specified in Javascript code and shouldn't have those restrictions.
2013-11-10docs($sce): ng-bind-html takes an expression `{{}}`Miško Hevery
2013-11-08fix(ngScenario): correctly disable animations for end 2 end testsPete Bacon Darwin
2013-11-08fix($animate): don't force animations to be enabledIgor Minar
The way that enabling of animations was set up, made it impossible to inject a module into the bootstrap to disable animations for things like end 2 end tests. Now animations are temporarily blocked by setting the animation state to RUNNING during bootstrap, which allows the developer to permanently disable at any point by calling $animate.enabled(false).
2013-11-08refactor($animate): speed up animationsDisabled checkIgor Minar
2013-11-07feat(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-07fix($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-07fix($compile): correct isolate scope distribution to controllersIgor 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-07fix($compile): replaced element has isolate scopeMisko Hevery
2013-11-07fix($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-07fix($compile): make isolate scope truly isolateVojta 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-07docs(guide/filter): Refactor filter guide docsTobias 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-06chore(docs): add -webkit-transition for ngClass exampleMatias Niemelä
generated by cgit v1.2.3 (git 2.25.1) at 2025-11-01 22:31:46 +0000