You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 20, 2020. It is now read-only.
Try switching for task-bar only for "a" to "b" (using buttons) you will see, that "a" exited, and "b" entered.
Now from "b" to "c" - same story. And this is OK.
Now, whilst task-bar.c is active, activate content.a, task-bar.c became inactive, whilst content.a activated. And this is OK.
Try activating content.b. You will see that task-bar.c remains inactive, content.a exiting, content.b activates. So far, good.
Now activate task-bar.d.
content.b -> inactive = OK
task-bar.d -> active = OK
task-bar.c -> inactive = Not OK
So, is this is on purpose?
If not, I believe I can create PR with fix. [ e861901 , a635b78 ] but not sure it will work with sticky inside sticky and other complicated scenarios.
The text was updated successfully, but these errors were encountered:
I see an issue, don't know if it's on purpose, But I will try to explain.
Plunker: http://plnkr.co/edit/iovSdLG52ezYgsfn46BU
There're two sticky states (task-bar / content)
So, is this is on purpose?
If not, I believe I can create PR with fix. [ e861901 , a635b78 ] but not sure it will work with sticky inside sticky and other complicated scenarios.
The text was updated successfully, but these errors were encountered: