| Age | Commit message (Collapse) | Author |
|---|
|
jQuery switched to a completely new event binding implementation as of
1.7.0, centering around on/off methods instead of previous bind/unbind.
This patch makes jqLite match this implementation while still supporting
previous bind/unbind methods.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
$route, $routeParams and ngView have been pulled from core angular.js
to angular-route.js/ngRoute module.
This is was done to in order keep the core focused on most commonly
used functionality and allow community routers to be freely used
instead of $route service.
There is no need to panic, angular-route will keep on being supported
by the angular team.
Note: I'm intentionally not fixing tutorial links. Tutorial will need
bigger changes and those should be done when we update tutorial to
1.2.
BREAKING CHANGE: applications that use $route will now need to load
angular-route.js file and define dependency on ngRoute module.
Before:
```
...
<script src="angular.js"></script>
...
var myApp = angular.module('myApp', ['someOtherModule']);
...
```
After:
```
...
<script src="angular.js"></script>
<script src="angular-route.js"></script>
...
var myApp = angular.module('myApp', ['ngRoute', 'someOtherModule']);
...
```
Closes #2804
|
|
|
|
Add a hint to tell the user that they need to click 3 times before an alert is shown.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Improved developer guide, directive unit testing documentation code with scope expression
* Removed documentation block with nothing on it
|
|
Fixes #2644.
|
|
|
|
element(selector, label).query(fn) is a very useful function, yet barely
explained. The developer guide should show how this function can be used
to conditionally execute behavior and assertions.
|
|
If a compile function (within a directive) returns a function, it is a
post-link function.
Closes: #2713
|
|
Closes #1316
|
|
"The compilation process happens into two phases." should be "The compilation process happens in two phases."
|
|
|
|
Matchers are briefly mentioned in the e2e test guide, but there is no
documentation for the available matchers.
|
|
|
|
When you are watching the $location.path(), it has to be wrapped in a
function since it is not attached to the scope and if you pass a string
to $scope.$watch it is evaluated against the $scope.
|
|
The examples in the angular-seed project are better than nothing,
which is what we currently have here!
|
|
Remove the outdated info in this document related to this API change
https://github.com/angular/angular.js/blob/master/src/ng/rootScope.js#L166
|
|
|
|
|
|
Closes: #1163
|
|
Specifically adding a directive controller to the example definition
and how to use declare injectables to avoid minification errors.
|
|
Current build process leverages closure jar for javascript minification.
If Java is not installed and included in the PATH the build will fail.
|
|
|
|
|
|
In the example with draggable, the mouseDown handler needs to start with an event.preventDefault(). Otherwise the following bug occurs:
1) Select the text of the draggable span by clicking outside the span and dragging the mouse to the left or right through the span. Release the mouse button.
2) Now click on the span's inner text, and start to Drag it. The browser's default functionality that drags highlighted text so that it can be pasted into something else (say a document in a text editor) is invoked.
3) Release the mouse button. Now suddenly, you'll be dragging the span. But you won't be able to place it down on the page. It'll just follow the mouse around until the page is refreshed.
Closes: #2465
|
|
Note that without this fix, if you add a second draggable element, the
two instances clobber each other since there is only one set of
startx/starty/x/y variables.
Here is an example: http://plnkr.co/edit/aGrLXcIo2SuaePuAdfmQ?p=preview.
On the surface it looks like it would be fine because you only have one
mouse but in practice the start position jumps when you start dragging.
Here it is fixed: http://plnkr.co/edit/VuvPasuumtCeiVRisYKQ?p=preview
|
|
|
|
|
|
|
|
|
|
The documentation says that the input should be red if you enter
invalid values or leave it blank. Because the type="integer" is not
supported this does not happen in practice. This fix changes the
input type to number and adds an ng-pattern to ensure that the number
is an integer.
|
|
The code snippet shows `{{action.description}}`, the explanation referred to it as `{{action.descriptions}}`.
|
|
|
