mirror of
https://github.com/syncthing/syncthing.git
synced 2024-11-16 10:28:49 -07:00
ed4807d9a4
The directive lives in its own isolated scope (where we put the visible() function). The stuff transcluded into the notification directive lives in the root scope and doesn't have access to the directive scope. Hence we cannot call dismiss() from inside the directive. Similarly, config does not exist by itself in the directive scope, we need $parent to access the root scope. Reference: https://docs.angularjs.org/guide/directive#isolating-the-scope-of-a-directive How this worked before is a mystery. My guess is Angular bug with directive scope that was fixed in 1.3. One possibility is that transclude plus scope: true (which doesn't make sense as that is supposed to be an object) resulted in the root scope being used in the directive itself. This would then "work" as long as there is only one notification, as visible() and dismiss() would then be registered on the root scope, thus accessible from within the notification but also overridden by any notification rendered. |
||
|---|---|---|
| .. | ||
| black/assets/css | ||
| dark/assets/css | ||
| default | ||