If the 'action' attribute is there, my-submit still not prevent default.
Without the action attribute, the user agent won't send your data. Consider
sending your form via XHR and FormData instead, in order to send the form
exactly as the browser would normally, without triggering navigation.
ng-bind-html does not compile the html template, it just sanitizes and renders
it. So, directives like ng-src won’t work. You might want to use ngInclude or a
router for this functionality instead.
On Apr 14, 2015, at 12:14 PM, Marco marco.sto...@gmail.com wrote:
Hello,
in my controller
Welcome to the world of CORS (Cross Origin Resource Sharing)!
You should be able to find a detailed explanation at the following resources:
http://enable-cors.org/ http://enable-cors.org/
http://www.html5rocks.com/en/tutorials/cors/
http://www.html5rocks.com/en/tutorials/cors/
Your `alertHi` method is not defined as a property of $scope.
The way ng-click works is, an expression (the value of the `ng-click`
attribute) is evaluated within the context of the nearest $scope. Variables
referenced in the expression need to exist in $scope or on its prototype chain.
Here’s
.
I'm a little fuzzy on global vs local $scope.
Is the fact that '$scope' a literal make it a local variable?
Thanks.
On Tuesday, March 10, 2015 at 11:57:04 AM UTC-7, Caitlin Potter wrote:
This is a way of interacting with the injector (one of several). The string
literal containing ‘$scope
This is a way of interacting with the injector (one of several). The string
literal containing ‘$scope’ tells the injector that the parameter at index 0
(first item in the array) should be ‘$scope’ from the injector. ‘$scope’ isn’t
registered globally in the injector, it comes from locals (so,
/ injector?*
function($scope, $http) { *// global, registered w/ injector, and mapped
to local?*
// ...
}]);
On Tuesday, March 10, 2015 at 1:53:25 PM UTC-7, Caitlin Potter wrote:
So, there are 2 kinds of things that can be injected into a function:
- Things which are registered
There are some issues:
1) the angular object is not a function (eg, `angular(“App2”, [])` is not
workable because `angular` is not callable, simple typo)
2) the “otherController” controller is registered for the other injector
Here’s a working version: http://codepen.io/anon/pen/PwePme
On
Pinging this thread, because I don't think any conclusions have been made
yet.
I don't personally care a whole lot which the conventions end up being,
it's fine with me to do whatever. But, some other core team folks do need
to OK the approach so that this can be done, or decide that it's not
One of the things that I'm not super-keen on with these strategies (of
dummy or lightweight versions in core, with the main implementation
outside of core) is that it tightly couples core with the extra module, and
it frequently trips people up when they accidentally use incompatible
versions
We’re sort of making it up as we go — but the main goal is to have multiple
core team members say “sounds good, lets do that”. There’s no real “time
limit”, but things would move faster if we got there within a week.
There are a few things blocking this:
For me, I want to figure out solid
I suggested commenting here, because I think we can do a bit more to
improve interop with CommonJS. That said, yes, completely replacing the
module system with something else is not likely to be doable for 1.x.
On Tue, Jan 20, 2015 at 4:23 PM, Ben Clinkinbeard
ben.clinkinbe...@gmail.com wrote:
Just so it's clear, we're talking about what people expect, not commenting
on your patch itself where we've already had this exact discussion :)
I would like to find out what users are expecting from this, and what would
make the most sense for them
On Tuesday, 13 January 2015 22:53:59 UTC-5,
LGTM, but we still need to establish the conventions that people will expect
Is an npm module equivalent to an angular module?
If so, `require('angular-animate').directive(myDirective, ...);` should
register a new directive in the ngAnimate module. But, in this scenario,
`require('angular')`
14 matches
Mail list logo
