directives on an element see the 'new' scope created by a sibling directive

[tonypee]

When a directive creates a scope it seems confusing that it pollutes the other directives run on the element. I was under the impression that sibling directives communicated via a controller, but they seem to share scope too - is this desired?

I have been defining a controller as ctrl, and am finding that it overshadows the parent ctrl - which is unexpected. An isolated scope fixes this. It seems that the scope is leaked where it shouldnt be

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

[pkozlowski-opensource]

This is duplicate of #8539, you can see longer discussion in the mentioned issue. Let's centralize the discussion in there.