In version 1.0.0, if you give an element a directive with an isolation scope, it will isolate the scope for all directives on that element. For example, notice how my custom directive is preventing ng-model from working:
This is a regression. It worked fine in rc9.
This works as expected. The custom directive creates an isolate scope which then prevents the ng-model from seeing anything. since it is isolated. What exactly did you expect to see? If it worked before it was a bug.
Well I have at least one other person in this thread who also thought it should work the way I do, as well as someone talking about ugly work-arounds to make it work this way. I think our way should be supported.
I find the currently supported sort of isolation scope to be pretty useless. It would be much more useful if it isolated the directive from the template, rather than isolating part of the template from the rest of the template.
As a general rule you should not write to scope. Always write to an object which sits of scope. In other words your expression needs to have at least one '.' in it, and then there are no surprises.