Merge lp:~mterry/unity8/bleeding-infographic into lp:unity8
Status: | Merged |
---|---|
Approved by: | Michael Terry |
Approved revision: | 1599 |
Merged at revision: | 1608 |
Proposed branch: | lp:~mterry/unity8/bleeding-infographic |
Merge into: | lp:unity8 |
Diff against target: |
57 lines (+9/-0) 2 files modified
qml/Greeter/GreeterContent.qml (+1/-0) tests/mocks/libusermetrics/UserMetrics.cpp (+8/-0) |
To merge this branch: | bzr merge lp:~mterry/unity8/bleeding-infographic |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
PS Jenkins bot (community) | continuous-integration | Approve | |
Gerry Boland (community) | Approve | ||
Albert Astals Cid (community) | Abstain | ||
Daniel d'Andrada (community) | Needs Information | ||
Review via email: mp+249223@code.launchpad.net |
Commit message
Clip the infographic to its bounding box, instead of letting it bleed past the welcome page (visible when dragging the welcome page to the side).
I've also done a bit of cleanup for the mock infographic data:
- I've forced a very large data bubble on the right side of the screen so that this bug/fix can specifically be seen.
- I've added data for the has-pin user (so that tryShellWithPin shows infographic data).
- I've fixed a crasher in our mock libusermetrics when a user has no data but the user double-clicked on the infographic.
Description of the change
Clip the infographic to its bounding box, instead of letting it bleed past the welcome page (visible when dragging the welcome page to the side).
I've also done a bit of cleanup for the mock infographic data:
- I've forced a very large data bubble on the right side of the screen so that this bug/fix can specifically be seen.
- I've added data for the has-pin user (so that tryShellWithPin shows infographic data).
- I've fixed a crasher in our mock libusermetrics when a user has no data but the user double-clicked on the infographic.
= Checklist =
* Are there any related MPs required for this MP to build/function as expected? Please list.
No
* Did you perform an exploratory manual test run of your code change and any related functionality?
Yes, you can see it clearly with tryShell or tryShellWithPin
* Did you make sure that your branch does not contain spurious tags?
Yes
* If you changed the packaging (debian), did you subscribe the ubuntu-unity team to this MP?
NA
* If you changed the UI, has there been a design review?
NA
Are you aware of the performance impact caused by clipping? Isn't there any other way to achieve what you need?