I'm in the same boat as Chris. Need to be sure I can embed my component with my angular and conflict with embedder's angular.
On Wednesday, October 23, 2013 7:09:20 AM UTC-4, Chris Dew wrote: > > +1 I need this for components too. > > On Wednesday, 24 April 2013 04:02:13 UTC+1, Dan McGhan wrote: >> >> I agree with Cam. >> >> Developers don't always have control over what others are doing in a web >> page, think CMS. What happens if multiple versions of Angular are used, >> which wins? A method like jQuery's noConflict should be easy enough as >> evidenced here: >> https://github.com/angular/angular.js/pull/1535 >> >> "Hopefully we will not do breaking changes" is a scary comment for a >> framework that wants to be taken seriously. It reminds me of how Twitter >> Bootstrap still doesn't support proper CSS scoping. >> >> Regards, >> Dan >> >> On Thursday, June 7, 2012 6:29:35 PM UTC-5, Vojta Jína wrote: >>> >>> I don't think we wanna do that. >>> >>> Hopefully now, we will not do breaking changes (at least not that often >>> :-D). >>> >>> V. >>> >>> On Fri, May 18, 2012 at 3:48 AM, Cameron Braid <cam...@braid.com.au> >>> wrote: >>> > Hi, >>> > >>> > Are there plans to support having multiple versions of angularjs >>> included on >>> > a single page. >>> > >>> > I am starting to use angular to write widgets that other people can >>> run on >>> > their site and my concern is that if their site uses angular as well >>> that >>> > there may be a conflict in the API of the two included versions. >>> > >>> > Initially I would like support for something like this - using osgi >>> style >>> > version ranges. The following declaring to use version 1.0 up to but >>> not >>> > including 1.1 >>> > >>> > <div ng-app='my-app' ng-version='[1.0,1.1)'> >>> > ... >>> > </div> >>> > >>> > This way I can code the my-app module to the 1.0 api and if the >>> hosting page >>> > includes angular 1.1 it won't break my widget. >>> > >>> > I realise that this could lead to quite a complex relationship between >>> > scopes if multiple versions are used in the same dom hierarchy >>> - however, >>> > the initial support could just address the simple case of separate >>> versions >>> > in separate dom hierarchies. >>> > >>> > Cam >>> > >>> > -- >>> > You received this message because you are subscribed to the Google >>> Groups >>> > "AngularJS" group. >>> > To post to this group, send email to ang...@googlegroups.com. >>> > To unsubscribe from this group, send email to >>> > angular+u...@googlegroups.com. >>> > For more options, visit this group at >>> > http://groups.google.com/group/angular?hl=en. >>> >> -- 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...@googlegroups.com. To post to this group, send email to angular@googlegroups.com. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/groups/opt_out.
