Hello lovely ng-nerds, You know how $scope is dependent on HTML element ordering and nesting? You also know how CSS layouts are dependent on HTML element ordering and nesting? Funny coincidence huh? It's also a pain point I just ran across while I was working on a dumb color picking app. I forsee this becoming an issue on ever complex Angular applications.
Let my dumb color picking app clarify the situation: http://plnkr.co/edit/2ynCHn?p=info Has anyone else run into this issue where they had to move a div out of a containing block for a style, but they couldn't because the containing block set the $scope you needed (or in my case, my template is just stuck in a ui-view)? I have a feeling that doing away with $scope hierarchies and binding your components directly with a model (provided by a service as a dependency) is the way to go. Best, i❤computers -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
