Visibility inheritance from Page to Groups (maybe a bug?)
Description
Actually this could be a bug. However I'm not sure about the desired behavrior so for now I set it as "feature request".
In my opinion, if I hide a page by setting an ui-control, I would expect all the child groups for this specifig hidden page were hidden as well. Instead, If I just hide all the pages on my dashboard, then the groups from my homepage are still displayed.
Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate
This is another example of unusual hierarchical auth missing:
Page 2 is disabled via ui-control:
{
"pages": {
"show": [
"Page 1", "Page 2"
],
"hide": [
],
"enable": [
"Page 1"
],
"disable": [
"Page 2"
]
}
}
However, if we go via direct url to /dashboard/page2 (immagine you push the browser back button after you executed a logic in your application that should have disabled the page 2) than going to that page is still possible, and the button (all the widgets) inside page 2 are now enabled.
I think the inheritance of enable/disable state should be the default here
I think the inheritance of enable/disable state should be the default here
Sensible