| 2015-01-09 14:34:57 |
Michael Sheldon |
bug |
|
|
added bug |
| 2015-01-09 14:36:39 |
Launchpad Janitor |
branch linked |
|
lp:~michael-sheldon/ubuntu-ui-toolkit/fix-1409027 |
|
| 2015-01-09 14:41:36 |
Michael Sheldon |
description |
The rewritten OrientationHelper that was merged into trunk here: http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/revision/1147 introduces a new 250ms timer to prevent incorrect rotations caused by Screen.primaryOrientation and Screen.orientation being set one after another. However this prevents applications from being able to rely on the changes to the angle having been applied via onOrientationAngleChanged (since they now only get applied 250ms after the orientation change happens).
Because the keyboard changes its orientation based on the application orientation this results in the keyboard rotating 250ms after the application has rotated, and more problematically means that the input area reported by the keyboard after the onOrientationAngleChanged being incorrect (as the orientation change hasn't actually happened).
Steps to reproduce
1) Open the browser
2) Tab the address bar
3) Rotate the phone
Expected outcome
All keys on the keyboard can be pressed
Actual outcome
Only keys in the old input area can be pressed because the new input area hasn't been reported. |
The rewritten OrientationHelper that was merged into trunk here: http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/revision/1147 introduces a new 250ms timer to prevent incorrect rotations caused by Screen.primaryOrientation and Screen.orientation being set one after another. However this prevents applications from being able to rely on the changes to the angle having been applied via the orientationAngleChanged signal (since they now only get applied 250ms after the orientation change happens).
Because the keyboard changes its orientation based on the application orientation this results in the keyboard rotating 250ms after the application has rotated, and more problematically means that the input area reported by the keyboard after the orientationAngleChanged signal being incorrect (as the orientation change hasn't actually happened).
Steps to reproduce
1) Open the browser
2) Tab the address bar
3) Rotate the phone
Expected outcome
All keys on the keyboard can be pressed
Actual outcome
Only keys in the old input area can be pressed because the new input area hasn't been reported. |
|
| 2015-01-09 14:45:05 |
Michael Sheldon |
description |
The rewritten OrientationHelper that was merged into trunk here: http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/revision/1147 introduces a new 250ms timer to prevent incorrect rotations caused by Screen.primaryOrientation and Screen.orientation being set one after another. However this prevents applications from being able to rely on the changes to the angle having been applied via the orientationAngleChanged signal (since they now only get applied 250ms after the orientation change happens).
Because the keyboard changes its orientation based on the application orientation this results in the keyboard rotating 250ms after the application has rotated, and more problematically means that the input area reported by the keyboard after the orientationAngleChanged signal being incorrect (as the orientation change hasn't actually happened).
Steps to reproduce
1) Open the browser
2) Tab the address bar
3) Rotate the phone
Expected outcome
All keys on the keyboard can be pressed
Actual outcome
Only keys in the old input area can be pressed because the new input area hasn't been reported. |
The rewritten OrientationHelper that was merged into trunk here: http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/revision/1147 introduces a new 250ms timer to prevent incorrect rotations caused by Screen.primaryOrientation and Screen.orientation being set one after another. However this prevents applications from being able to rely on the changes to the angle having been applied via the orientationAngleChanged signal (since they now only get applied 250ms after the orientation change happens).
Because the keyboard changes its orientation based on the application orientation this results in the keyboard rotating 250ms after the application has rotated, and more problematically means that the input area reported by the keyboard after the orientationAngleChanged signal is incorrect (as the orientation change hasn't actually happened).
Steps to reproduce
1) Open the browser
2) Tab the address bar
3) Rotate the phone
Expected outcome
All keys on the keyboard can be pressed
Actual outcome
Only keys in the old input area can be pressed because the new input area hasn't been reported. |
|
| 2015-01-12 13:43:56 |
Daniel d'Andrada |
description |
The rewritten OrientationHelper that was merged into trunk here: http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/revision/1147 introduces a new 250ms timer to prevent incorrect rotations caused by Screen.primaryOrientation and Screen.orientation being set one after another. However this prevents applications from being able to rely on the changes to the angle having been applied via the orientationAngleChanged signal (since they now only get applied 250ms after the orientation change happens).
Because the keyboard changes its orientation based on the application orientation this results in the keyboard rotating 250ms after the application has rotated, and more problematically means that the input area reported by the keyboard after the orientationAngleChanged signal is incorrect (as the orientation change hasn't actually happened).
Steps to reproduce
1) Open the browser
2) Tab the address bar
3) Rotate the phone
Expected outcome
All keys on the keyboard can be pressed
Actual outcome
Only keys in the old input area can be pressed because the new input area hasn't been reported. |
The rewritten OrientationHelper that was merged into trunk here: http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/revision/1147 introduces a new 250ms timer to prevent incorrect rotations caused by Screen.primaryOrientation and Screen.orientation being set one after another. However this prevents applications from being able to rely on the changes to the angle having been applied via the orientationAngleChanged signal (since they now only get applied 250ms after the orientation change happens).
Because the keyboard changes its orientation based on the application orientation this results in the keyboard rotating 250ms after the application has rotated, and more problematically means that the input area reported by the keyboard after the orientationAngleChanged signal is incorrect (as the orientation change hasn't actually happened).
Steps to reproduce
1) Open the browser
2) Tap the address bar
3) Rotate the phone
Expected outcome
All keys on the keyboard can be pressed
Actual outcome
Only keys in the old input area can be pressed because the new input area hasn't been reported. |
|
| 2015-01-15 10:17:01 |
Zsombor Egri |
ubuntu-ui-toolkit (Ubuntu): assignee |
|
Michael Sheldon (michael-sheldon) |
|
| 2015-01-15 10:17:08 |
Zsombor Egri |
ubuntu-ui-toolkit (Ubuntu): status |
New |
In Progress |
|
| 2015-02-09 09:18:25 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/vivid-proposed/ubuntu-ui-toolkit |
|
| 2015-02-09 21:40:08 |
Launchpad Janitor |
ubuntu-ui-toolkit (Ubuntu): status |
In Progress |
Fix Released |
|
