| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the forms/controls code refactored not to depend on events which forced
us to create new scope for each form element.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This reverts commit 8fb34f008eca4d1e15e6fa63902aaa36d199c4af.
|
|
|
|
|
|
so that we can render better usage examples in docs
|
|
the original code magically worked for ng:foo but for nothing else
|
|
we can't provide this functionality because the directives are lazy
loaded when the module loads, which is too late for the shiv to do
anything useful.
|
|
|
|
|
|
It registers a provider class, so this makes more sense.
Breaks Rename $provide.service -> $provide.provider
|
|
Each widget (ng-model directive) emits $newFormControl event instead of getting hold of parent form
and calling form.registerWidget(this);
|
|
|
|
|
|
- change custom onload directive to special arguments recongnized by both
ng-view and ng-include
- rename $contentLoaded event to $viewContentLoaded and $includeContentLoaded
- add event docs
|
|
|
|
|
|
I.e. constructor, toString, or watch on FF
(https://developer.mozilla.org/en/JavaScript/Reference/Global_Objects/Object/watch)
+ optimize parser a bit to not create getter function for operators
|
|
It's more likely you are using angular.fromJson() inside Angular world, which means you get proper
exception handling by $exceptionHandler.
There is no point to explicitly push it to console and it causes memory leaks on most browsers
(tried Chrome stable/canary, Safari, FF).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
And explicitly say that you need to load your application modules that you wanna test.
|
|
|