I call blame on Angular for this mess. Yes, I understand CORS is set on
the server but far too many people are having trouble with the
pre-flight handling on Angular. For us, code that worked on Backbone
did not work on Angular - there seems to be something in the way Angular
works that creat
with a single page application, is it more proper to have a typical
input form on a separate page ? Is there any data handling or
validation issue on one vs the other ? We've done it both ways and
don't see that much a difference
--
You received this message because you are subscribed to the
On 04/16/2014 10:14 AM, Neil Camara wrote:
That means, I need to include both. UI-router for accessing interface
neatly and $resource/restangular for my REST calls.
not really. you can make a rest call (ie /api/posts) directly within a
controller with $http without using $resource or restangu
On 02/20/2014 01:11 PM, Christopher Schulz wrote:
What am I doing wrong? I have read a million articles and can't get
it right
_
_
_
_
_
_ 'Access-Control-Allow-Credendtials': 'true', 'Content-
credentials is spelled wrong
--
You received this message because you are subscribed to the Googl
First, CORS is tricky, a PITA, so don't feel bad if you are having
problems.
JSONP is a good, easy solution for GET ting data. It does not work well
for PUT, POST, DELETE
Somewhere I've seen some angular examples with JSONP - test if you are
receiving data - then in what format the data is in
trying to do a simple blog feed - no errors reported in chrome, but no
feeds either. Did get a "return deprecated" error - and not sure how
the suggested event.preventDefault() should be used to resolve that.
wondering if $scope.blogs is accessed correctly between ctrl - factory -
service
a
tried to use with setTimeout to trigger it but it's not working - are
there any examples ? thks
--
You received this message because you are subscribed to the Google Groups
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to angular+unsubscr..
riginal Message-
From: angular@googlegroups.com [mailto:angular@googlegroups.com] On Behalf Of
john.tiger
Sent: venerdì 10 gennaio 2014 17:46
To: angular@googlegroups.com
Subject: Re: Fw: Re: [AngularJS] Bootstrap nav bar issues - still serious issue
w/ angular
here's the key code in
it seems that new version updates just appear quietly on the download
site (it seems it's up to 1.2.8 now) - it would be really helpful if
the core team could post an announcement here along with the update log
and any comments as to how critical the update is. Nodejs does an
excellent job of
trap
nav bar issues - still serious issue w/ angular From: Mauro Servienti
To: "angular@googlegroups.com"
CC: Can you show a failing plunker, because
I¹m using ³nav² all the time without any issue at all. .m On 09/01/14
21:42, "john.tiger" wrote:
maybe it's the lack
maybe it's the lack of a good example, maybe a case of dismissing common
webpage layouts, but the inability of using bootstrap navbar is a
showstopper for using angular - we can use angular without bootstrap but
for several sites want to use bootstrap.
specifying a route of route config leads
fyi: we deleted the angular-ui as still too buggy - since we were mostly
interested in just having navbar collapse working in addition to the
css, we just followed another post (can't remember where) on using an
ng-class for navCollapse and toggling it with ng-click - now the navbar
collapse
navbar shows but data is not loaded and dropdowns not working when
index.html is opened with chromium (debian testing). seems similar to
problems we've had with angular and bootstrap. any ideas on how to fix ?
--
You received this message because you are subscribed to the Google Groups
"Angu
13 matches
Mail list logo
