Permalink
Commits on Mar 14, 2016
Commits on Mar 13, 2016
Commits on Mar 11, 2016
-
Component Router should come after the menu topic Components as Components should be understood first before Component Routers. This made it easier to read the Component Routers topic. Closes #14214
-
Narretz committed
Mar 10, 2016 Removes the bullet points and makes all prompts bold, which should make it easier to see which content has been added by the issue author
Commits on Mar 8, 2016
Commits on Mar 7, 2016
Commits on Mar 4, 2016
Commits on Mar 2, 2016
Commits on Mar 1, 2016
Commits on Feb 29, 2016
-
When an error message contains an HTML string (e.g. `$location:nobase` containing `<base>`), it was interpreted as a literal HTML element, instead of text. Error messages are not expected to render as HTML, but we still need to use `.html()` in `errorDisplay`, so that the links created by `errorLinkFilter` are properly displayed. This commit solves this issue by replacing `<`/`>` with `<`/`>`. Related to #14016.
Commits on Feb 28, 2016
-
We don't set selected property / attribute on options that are already selected. That happens for example if the browser has automatically selected the first option in a select. In that case, the selected property is set automatically, but the selected attribute is not. This doesn't impact the functionality of the select, but it can be problematic if option elements are selected with `option[selected]` in tests. Closes #14115 Closes #14125
-
-
A factory that doesn't return anything is a bad example of a factory. Closes #14139
-
Narretz committed
Feb 28, 2016 - highlight that interpolation inside expressions is bad practice - add info about type attr in buttons in IE
Commits on Feb 25, 2016
-
…bled is false When debugInfoEnabled is `false` when comments generated by transclusions, ngIf, ngRepeat and ngSwitch will not contain any information about the directive nor the expression associated with it. Closes: #8722
-
…ed template During it's linking phase, `ngView` relies on the info provided in `$route.current` for instantiating the initial view. `$route.current` is set in the callback of a listener to `$locationChangeSuccess`, which is registered during the instantiation of the `$route` service. Thus, it is crucial that the `$route` service is instantiated before the initial `$locationChangeSuccess` is fired. Since `ngView` declares `$route` as a dependency, the service is instantiated in time if `ngView` is present during the initial load of the page. Yet, in cases where `ngView` is included in a template that is loaded asynchronously (e.g. in another directive's template), the directive factory might not be called soon enough for `$route` to be instantiated before the initial `$locationChangeSuccess` event is fired. This commit fixes it, by always instantiating `$route` up front, during the initialization phase. Fixes #1213 Fixes #6812 Closes #14088
Commits on Feb 24, 2016
Commits on Feb 23, 2016
-
-
Previously, `angular-mocks` was calling `$rootScope.$destroy()` after each test as part of it's cleaning up, assuming that it was always available. This could break if `$rootScope` was mocked and the mocked version didn't provide the `$destroy()` method. This commit prevents the error by first checking that `$rootScope.$destroy` is present. Fixes #14106 Closes #14107
-
This means that we can access these annotations, such as `$routeConfig` and `$routerCanActivate` without highjacking the `ng` module. Closes #14114
