Comment 0 for bug 1408015

Imagine a form of some sort, you fill a few fields of data top-down, and at the end of it you need to tap in the header at the top to save/confirm.

Pair that with the header going off-screen to leave more screen for the content, you have to pull the header in first (and you need to know that's where the button will be).

An example of this behaviour is the calendar app when adding/editing an event. One other example (although that could be improved easily by auto-saving the new note as soon as it's edited) is the Quick Memo app, where when you create a note in the first place you need to tap the ✓ icon, but when you're editing, it's all auto-saved and you need to tap 〈 to go back to the list of notes.

I feel like we need to at least come up with clear guidance on what belongs in the header, and where a footer with buttons should be used (we have a way to stick something on top of the keyboard after all¹).

http://developer.ubuntu.com/api/qml/sdk-1.0/Ubuntu.Components.MainView/#anchorToKeyboard-prop

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 1.1.1364+15.04.20141209-0ubuntu2
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.15-0ubuntu3
Architecture: armhf
Date: Tue Jan 6 17:03:54 2015
InstallationDate: Installed on 2014-12-17 (20 days ago)
InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141217-020204)
SourcePackage: ubuntu-ui-toolkit
UpgradeStatus: No upgrade log present (probably fresh install)