Carousel renderer flies off the screen when scrolling on N10
Bug #1279453 reported by
Chris Wayne
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
The Savilerow project |
Won't Fix
|
Undecided
|
Unassigned | ||
unity8 (Ubuntu) |
Fix Released
|
High
|
Andrea Cimitan |
Bug Description
WHen using new-scopes api on nexus 10, trying to scroll a carousel acts very strangely, as the entire carousel seems to fly away off the screen. See attached video
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity8 (not installed)
ProcVersionSign
Uname: Linux 3.13.0-8-generic x86_64
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Feb 12 13:14:38 2014
InstallationDate: Installed on 2013-07-26 (200 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: unity8
UpgradeStatus: Upgraded to trusty on 2013-11-21 (83 days ago)
Related branches
lp:~unity-team/unity8/new-scopes-carousel-bounds-patch
Rejected
for merging
into
lp:~unity-team/unity8/new-scopes
- Michał Sawicz: Disapprove
- Andrea Cimitan (community): Needs Fixing
- Albert Astals Cid (community): Needs Information
-
Diff: 12 lines (+1/-1)1 file modifiedqml/Components/Carousel.qml (+1/-1)
lp:~unity-team/unity8/new-scopes.carousel-dinamic-fallback
Rejected
for merging
into
lp:~unity-team/unity8/new-scopes
- Michał Sawicz: Disapprove
-
Diff: 318 lines (+105/-52) (has conflicts)7 files modifiedqml/Dash/CardCarousel.qml (+3/-11)
qml/Dash/CardFilterGrid.qml (+2/-12)
qml/Dash/CardTool.qml (+42/-10)
qml/Dash/DashRenderer.qml (+5/-0)
qml/Dash/GenericScopeView.qml (+33/-4)
tests/qmltests/Dash/tst_CardTool.qml (+20/-0)
tests/qmltests/Dash/tst_GenericScopeView.qml (+0/-15)
Changed in unity8 (Ubuntu): | |
assignee: | nobody → Michał Karnicki (karni) |
importance: | Undecided → High |
Changed in unity8 (Ubuntu): | |
assignee: | Michał Karnicki (karni) → Andrea Cimitan (cimi) |
Changed in unity8 (Ubuntu): | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.