Closed hex closed 11 years ago
Apologies for the inconveniences you've had lately - you've successfully covered quite a few corner cases. I implement automatic test cases for each of this along with the fixes. That should prevent regression in the future.
As a workaround proposal / question. Do you need specifically element.transparency.model
in the directives? The same object is available through this
reference. And after rendering, element.transparency.model
is available as usual. Please see http://jsfiddle.net/wyygS/16/ for the demonstration.
That said, I definitely agree it's logical and consistent to have element.transparency.model
available in directive functions, too. So, will fix.
Thanks for the invaluable and accurate issue reports!
Fixed in v0.8.2.
I am experiencing a strange behaviour in v0.8.1. I made two fiddles:
(using v0.7.11) > http://jsfiddle.net/hexaust/XG7Gk/ (using v0.8.0) > http://jsfiddle.net/hexaust/wyygS/
As you can see the output of the console.log is different, one returns the object and the other one says 'undefined'.
I hope I am making this clear I don't know how to describe the issue in any other way. Thanks!