Using ng-if directive at the root node of a view messes up the destroy()

[mehmetf]

No description provided.

[mehmetf]

Perhaps this is related to bug #704. When I do something like this:

   bind(RouteInitializerFn, toValue: (Router router, RouteViewFactory views) {
      views.configure({
        'view1': ngRoute(path: '/view1',
            viewHtml: '<div ng-if="true"><h2>View 1</h2></div>'),
        'view2': ngRoute(path: '/view2',
            viewHtml: '<div ng-if="true"><h2>View 2</h2></div>'),
      });
    });

and with html file:

    <a href="#/view1">Switch to View 1</a>
    <a href="#/view2">Switch to View 2</a>
    <div>
      <ng-view></ng-view>
    </div>

I get this switching back and forth views:

Removing ng-if directive fixes the problem.

I am trying to do this as a workaround for animating the view transitions. ng-if="true" allows the root node to be injected to DOM via viewport and animates the view.

[naomiblack]

This looks like a bug. We're going to defer until after 0.15 -- as a workaround, if you enclose your HTML in a <div> tag, you should see this work as expected.

<div>
   <a href="#/view1">Switch to View 1</a>
    <a href="#/view2">Switch to View 2</a>
    <div>
      <ng-view></ng-view>
    </div>
</div>

[mehmetf]

You mean wrap the views with

's:

  bind(RouteInitializerFn, toValue: (Router router, RouteViewFactory views) {
      views.configure({
        'view1': ngRoute(path: '/view1',
            viewHtml: '<div><div ng-if="true"><h2>View 1</h2></div></div>'),
        'view2': ngRoute(path: '/view2',
            viewHtml: '<div><div ng-if="true"><h2>View 2</h2></div></div>'),
      });
    });

Yes, this works.