| Age | Commit message (Collapse) | Author |
|---|
|
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
|
|
|
|
|
|
Specifically adding a directive controller to the example definition
and how to use declare injectables to avoid minification errors.
|
|
|
|
|
|
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}}`.
|
|
|
|
|
|
|
|
Default hashPrefix setting is not `'!'`, it's actually `""`.
Source: https://github.com/angular/angular.js/blob/master/src/ng/location.js#L472
|
|
|
|
An event is a user **interaction**, timer event, or network event (response from a server).
|
|
... or when working with --> a <-- third-party library callbacks.
... or when working with third-party library callbacks.
|
|
|
|
|
|
|
|
|
|
|
|
Add example of using a filter with that accepts multiple arguments.
|
|
- note re: id="ng-app" to bootstrap/IE partials
- added doctype/xmlns to markup
- add cond comment re: json2/3 to markup
|
|
|
|
|
|
|
|
|
|
docs(forms): Fixed a typo. render -> $render
|
|
|
|
Changed "obeject" to "object"
|
|
Replace an obsolete reference to a nonexistent "Creating Widgets"
section with a real link to "Creating Components".
|
|
Use double quotes to maintain consistency with other HTML
|
|
|
|
as of v0.10.6 this is not the case any more
|
|
|
|
As explained in 'Understanding the Controller Component', Controllers
written for new (post 1.0 RC) versions of Angular need to add methods to
the scope directly, not the function's prototype. Correcting this
example should remove any ambiguity, especially for beginners.
|
|
|
|
|
|
|
