seems to behave a bit strangely, especially its interaction with the global ApplicationHeader is quite strange

In D2306#42989, @mart wrote:

seems to behave a bit strangely, especially its interaction with the global ApplicationHeader is quite strange

What is that you don't like exactly? I can look into it if you tell me.

In D2306#43005, @apol wrote:

In D2306#42989, @mart wrote:

seems to behave a bit strangely, especially its interaction with the global ApplicationHeader is quite strange

What is that you don't like exactly? I can look into it if you tell me.

it should just be a fixed header, always visible and laid out with the main content or flickable, it should be in Page (and just happening to work in scrollablepage too) and the property called just header, not pageHeader

ie it has to be as much identical as possible to
http://doc.qt.io/qt-5/qml-qtquick-controls2-page.html

because Page is going to inherit from that one in the future

In D2306#43024, @mart wrote:

it should just be a fixed header, always visible and laid out with the main content or flickable, it should be in Page (and just happening to work in scrollablepage too) and the property called just header, not pageHeader

ie it has to be as much identical as possible to
http://doc.qt.io/qt-5/qml-qtquick-controls2-page.html

because Page is going to inherit from that one in the future

I'm not sure that's what I need. Should I implement it in Discover and when we move to Qt 5.7 we see what should be upstreamed, if anything?