autoscrolling not working in online accounts
Bug #1413765 reported by
Bill Filler
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
High
|
Unassigned | ||
Online Accounts setup for Ubuntu Touch |
Fix Released
|
High
|
Alberto Mardegan | ||
webbrowser-app |
Invalid
|
High
|
Olivier Tilloy | ||
ubuntu-system-settings-online-accounts (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
ubuntu-system-settings-online-accounts (Ubuntu RTM) |
Fix Released
|
Undecided
|
Alberto Mardegan |
Bug Description
krillin rtm build 208
clicking in entry field in an online accounts embedded webpage is not causing the field to scroll into view as it does when loading in webbrowser-app
Steps to reproduce:
- create a new Google online account
- click on the username/email field
- the OSK is displayed
Expected result:
- the entry field that has focus should be scrolled into view and unobstructed
Actual result:
- the entry field is not scrolled and partially obstructed
This same thing works when done directly in the browser. Not sure if the issue is browser related, or something to do with the container.
Related branches
lp://staging/~mardy/ubuntu-system-settings-online-accounts/lp1413765
Merged
into
lp://staging/~online-accounts/ubuntu-system-settings-online-accounts/master
at
revision 223
- David Barth (community): Approve
-
Diff: 13 lines (+1/-2)1 file modifiedplugins/module/OAuth.qml (+1/-2)
lp://staging/~mardy/ubuntu-system-settings-online-accounts/lp1413765-rtm
- Alberto Mardegan (community): Approve
-
Diff: 13 lines (+1/-2)1 file modifiedplugins/module/OAuth.qml (+1/-2)
Changed in ubuntu-system-settings-online-accounts: | |
importance: | Undecided → High |
assignee: | nobody → Alberto Mardegan (mardy) |
Changed in webbrowser-app: | |
importance: | Undecided → High |
assignee: | nobody → Olivier Tilloy (osomon) |
Changed in webbrowser-app: | |
status: | New → Invalid |
Changed in ubuntu-system-settings-online-accounts (Ubuntu): | |
status: | New → Fix Released |
Changed in canonical-devices-system-image: | |
importance: | Undecided → High |
milestone: | none → ww07-2015 |
status: | New → Confirmed |
Changed in ubuntu-system-settings-online-accounts (Ubuntu RTM): | |
assignee: | nobody → Alberto Mardegan (mardy) |
status: | New → In Progress |
Changed in canonical-devices-system-image: | |
status: | Confirmed → In Progress |
Changed in canonical-devices-system-image: | |
status: | In Progress → Fix Released |
Changed in ubuntu-system-settings-online-accounts: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
I can confirm the issue on krillin image #209.
I had a quick look at the code, and the webview is inside a Loader whose anchors are defined like so:
Loader {
bottomMarg in: Math.max(osk.height - cancelButton. height, 0)
anchors {
bottom: cancelButton.top
}
}
If I remove the bottomMargin, and bind the bottom anchor to osk.top, the field is scrolled into view as expected. So somehow the bottomMargin is causing oxide to not be notified of the height change in time.
This should be easy enough to fix by making the bottom anchor conditional (depending on the OSK’s visibility), or by making both the OSK and cancel button children of an item and anchoring the webview to that item.