Alberto, I disagree with your solution. I think the behavior that we have now is correct because it keeps the original topMargin of the flickable for the part of the flickable that will be visible below the header (in y-direction).
Your video shows a very special case: A Page with a header, and a horizontal ListView in which there are vertical Flickables that are attached to the Page.header (depending on which Flickable is the current item in the ListView). Personally in that case I would use a locked header (don't link it to a flickable), but I think you should talk to design about it. If this were to become a common pattern, I would like to see design guidelines on how to deal with this, and then we can discuss the technical aspects of the proposal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572525 Title: [regression] Double header height is set as flickable topMargin To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1572525/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
