Comment 2 for bug 1518002

Tim Peeters (tpeeters) wrote :

With the current header configuration using Page.head there is this issue, and other issues related to the configuration of more customized header. We introduced a new Page.header property (in UITK staging, soon to land in trunk) that can be set to any Item to have your own header, and if you set it to an instance of the new PageHeader component, it will look the same as the current header. It will require changing some code (not much) related to the header, but after doing that you will have a lot more flexibility in what you can do with the header, including properly hiding/disabling it.

The current API will keep working in UITK 1.3, as long as you don't set the Page.header property, the old header will appear for your page. But I will recommend apps to switch to the new header once we have it landed in an image. The documentation for the header will be included in UITK docs at the same time the new features land.