Hi mówMiStefan,
I do see the behaviour you are describing, and have no explanation. I suspect that as select is an angular directive, something goes haywire if you replace it with your own directive. (that has also an select inside..). However, why did you choose the attribute model for this directive? If you use the element model, your problem is solved to, and you don’t need to replace your root node. something like: <custom-select type='some.Type' ...></custom-select> I think this is a cleaner form of the directive! Regards Sander -- 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/groups/opt_out.
