Comment 0 for bug 1659869

We have been discussing on IRC about the focus path on page header-> page-contents.

Some apps require a fine tuning on the focus path for the header buttons and contents. This is not possible today since we do not have access to all header objects (only actions).

Another problem is that the page first receive focus on your contents and after the header (check image0.png). This can be annoying if the focus starts on the header because the focus go to another page before enter on page contents (check image1.png). would be nice to allow apps to choose which is the desired focus paths between pages and headers.

And in the end would be nice to have a AdaptativePageLayout method to allow user to access a page pages on index or something else in case of the user want to move focus to a different page in the stack.