prevent elements are bootstrapped more than once#2
prevent elements are bootstrapped more than once#2revington wants to merge 1 commit intoluisperezphd:masterfrom
Conversation
|
Do we know why exactly this happens? I'm running into the same issue and need to solve it ASAP. |
|
Hey Derek, I'm not sure what you are referring to. On Thu, Aug 13, 2015 at 5:30 PM, Derek Dowling notifications@github.com
|
|
Hey everyone, I'm sorry I'm just getting familiar with GitHub was not aware of this "conversation" section. Can you provide an example of the issue. A JSFiddle for example stripped down to the core problem so I can recreate and really understand the issue. |
|
So this appears to be where the check was introduced: angular/angular.js#3411. I'm still trying to figure out what reproduces it on my end. |
|
I've got this problem in the past. Solved with this patch and never faced the issue again. Since the PR was never merged I've been using my fork until today. |
|
I had the same problem, i''m using your fork now revington, thanks! |
|
@alex-LE My branch is outdated but it works for me in production. |
An element like
will generate an error like Uncaught Error: [ng:btstrpd] App Already Bootstrapped with this Element '<div ng-module="UserNotfications" ng-controller="UserNotificationsCtrl" class="ng-scope">
Also:
Is the class important? I'm a newbie in angular, but as far as I know the class is not used to glue the controllers nor the modules. Should I keep it or remove it?