Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

Using ngTransclude creates 2 isolate scopes instead of one #4925

@ryanzec

Description

@ryanzec

Not sure if this is a bug but it seems like one to me. First example:

http://plnkr.co/edit/54J6FKRobsctMNrErVeX?p=preview

This is using transclusion and uses the ngTransclude directive to perform the transclusion. The issue I am seeing that when inside the compile function (or really linking function), the scope.$id is 004 however when I try to access scope.$id directly inside the template, I get 005.

Here is a second example:

http://plnkr.co/edit/lUYDhb6oBVjiOdpFvtxX?p=preview

In this example I am still using transclusion however I am manually performing the transclude process but it gives me the expected scope.$id when I try to access it directly inside the template.

Is this a bug with the ngTransclude directive?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions