Actually the Page does not fill its parent, but anchors to all sides except the top, and the Page.height depends on the parent, the header, and whether the Page has a flickable. As long as we don't move the header into the page, I don't see a better solution than what we have now. If we don't anchor it to parent.bottom, then we need to offset its y depending on the header.
That said, if the header goes into the page, we could set implicitWidth and implicitHeight of the Page instead of anchoring, or don't set any anchors/width/height at all (although mostly it will have to fill its parent). Anyway, I don't think any choice we make will fix the current bug, so that's a separate discussion. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1492343 Title: Pages hidden in an AdpativePageLayout stack have their width changed to zero Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: As shown in this example [0], if you select the "Albums for artist" button to push a page onto the stack, you can see in the console that the width of the old component is changed to zero, which causes it then to reflow as the width is increased when it is brought back into view. Instead, the width should not be changed when the page is hidden. 0 - http://pastebin.ubuntu.com/12274053/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1492343/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp