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
I was lately trying to implement a Tabbar component such as this one
<#tabbar selected="{selected}"><@tab label="Tab1">This is tab 1</@tab><@tab label="Tab2">This is tab 2</@tab><@tab label="Tab3">This is tab 3</@tab></#tabbar>
It appears that when the property ctrl.selectedcontent is updated, the corresponding onSelectedcontentChange() is called, but the child component inclusion is apparently not refreshed, which is not the awaited behavior
PS: ideally I would even have written that in the first place <#ctrl.content[ctrl.selected].body /> and be waiting for the same refresh to occurs but unfortunately it is not supported as well for now...
The text was updated successfully, but these errors were encountered:
@b-laporte I had a look to lines 554-611 in $root.js, and I am wondering: isn't this duplicating code? Isn't a template path an expression? Couldn't it be observed by the expression handler, just like expressions in text nodes and others?
I was lately trying to implement a
Tabbar
component such as this oneConsider the following source code
It appears that when the property
ctrl.selectedcontent
is updated, the correspondingonSelectedcontentChange()
is called, but the child component inclusion is apparently not refreshed, which is not the awaited behaviorPS: ideally I would even have written that in the first place
<#ctrl.content[ctrl.selected].body />
and be waiting for the same refresh to occurs but unfortunately it is not supported as well for now...The text was updated successfully, but these errors were encountered: