| Age | Commit message (Collapse) | Author |
|---|
|
Broken by fd7bca22e16b0ecbe1feaf49bab39d9a44b8df01
|
|
Closes #4948
|
|
Closes #4936
|
|
Backslash is acting as escape character so text is not properly formatted.
Closes #4923
|
|
Closes #4918
|
|
Closes #4914
|
|
$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
|
|
Before:
> Let's add some more logic to the example to
allow to enter and calculate the costs in different currencies and also pay the invoice.
After:
> Let's add some more logic to the example that
allows us to enter and calculate the costs in different currencies and also pay the invoice.
Closes #4903
|
|
Closes #4900
|
|
Closes #4854
|
|
|
|
Closes #4873
|
|
'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
|
|
Closes #4860
|
|
Closes #4848
|
|
Closes #4846
|
|
The `<doc:example>` directive does not load up the dependencies correctly.
Using the `<example>` directive, with `<file>` elements fixes this.
Closes #4951
|
|
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
|
|
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
|
|
|
|
Update the $compile docs to mention the change introduced in #4266.
Closes #4843
|
|
Remove reference to `employee` property as it's not used in the example.
Inject and use `$rootScope` applying `department` property as mentioned in text.
Closes #4839
|
|
The CSS styling in the ng-scope demo was using CSS classes (`.doc-example-live` and
`.show-scope') to prevent the styling for the demo from affecting the entire page.
Unfortunately elements containing these classes did not appear in JSFiddle or Plunker
when you click edit.
This fix moves the `.show-scope' class inside the demo (renaming it `.show-scope-demo`)
and removes the reliance on `.doc-example-live` altogether.
Closes #4838
|
|
This message needs a justification. Without one, it's like asking somebody
on *nix to run everything under sudo 'just because'.
Closes #4832
|
|
Closes #4830
|
|
HTML elements were getting parsed by as HTML elements
Closes #4827
|
|
Closes #4821
|
|
Correct " model property `spice` " to " model property `customSpice` " to match the code sample
Closes #4812
|
|
Closes #4811
|
|
Make the possibility to pass a custom cache instance to $http more obvious.
Closes #4803
|
|
Closes #4793
|
|
Closes #4792
|
|
The grouping of the different versions was not correct for the new 1.2.0+ releases.
Now versions are marked as stable only if they have an even number it the minor version
position (e.g. 1.0.8, 1.2.1, 1.2.0-abcde) and they are not an RC version, (e.g. 1.0.0rc3,
1.2.0-rc2).
Closes #4908
|
|
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
|
|
A directive with a template with `replace: true` and an interpolated style at the root element should work correctly.
Closes #4882.
|
|
|
|
another thruthy value.
Fixes #4852.
|
|
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.
|
|
|
|
|
|
|
|
The marked npm library brought in a breaking change at 0.2.10.
This commit ensures that we get exactly the version we want.
Closes #4822
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
