[QtComp] Vkb stays above indicators panel
Bug #1346330 reported by
Daniel d'Andrada
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| unity8 (Ubuntu) |
Fix Released
|
Undecided
|
Daniel d'Andrada | ||
Bug Description
1-open an app
2-focus a text entry there
* Virtual keyboard slides in
3 - pull down the indicators panel
Expected outcome:
Panel lies in front of both the vkb and the app
Actual outcome:
vkb stays in front of the panel.
Related branches
lp:~unity-team/unity8/mirCompositor
- Gerry Boland (community): Approve
- PS Jenkins bot (community): Needs Fixing (continuous-integration)
- Michael Zanetti (community): Approve (c++ code review)
- Michael Terry: Approve (debian-packaging)
- Vesa Rautiainen (community): Approve (design)
-
Diff: 6483 lines (+3413/-1522)52 files modifieddebian/changelog (+14/-0)
debian/control (+1/-2)
plugins/Utils/CMakeLists.txt (+1/-0)
plugins/Utils/easingcurve.cpp (+5/-1)
plugins/Utils/plugin.cpp (+2/-0)
plugins/Utils/windowkeysfilter.cpp (+57/-0)
plugins/Utils/windowkeysfilter.h (+51/-0)
qml/Components/Dialogs.qml (+217/-0)
qml/Components/DraggingArea.qml (+4/-0)
qml/Components/InputMethod.qml (+79/-0)
qml/Components/PageHeader.qml (+3/-1)
qml/Dash/Apps/RunningApplicationTile.qml (+45/-37)
qml/Dash/DashContent.qml (+4/-0)
qml/Launcher/Launcher.qml (+1/-1)
qml/Panel/Indicators.qml (+3/-0)
qml/Shell.qml (+171/-393)
qml/Stages/Animations/BaseSurfaceAnimation.qml (+93/-0)
qml/Stages/Animations/DarkenAndFadeInAnimation.qml (+48/-0)
qml/Stages/Animations/SwipeFromBottomAnimation.qml (+48/-0)
qml/Stages/Animations/SwipeUpAnimation.qml (+49/-0)
qml/Stages/PhoneStage.qml (+173/-265)
qml/Stages/SidestageHandle.qml (+0/-22)
qml/Stages/Splash.qml (+68/-0)
qml/Stages/SpreadDelegate.qml (+193/-29)
qml/Stages/StageWithSideStage.qml (+0/-413)
qml/Stages/SurfaceContainer.qml (+123/-0)
qml/Stages/SwitchingApplicationImage.qml (+0/-81)
qml/Stages/TabletStage.qml (+568/-0)
qml/Stages/TransformedSpreadDelegate.qml (+36/-30)
qml/Stages/TransformedTabletSpreadDelegate.qml (+369/-0)
src/CMakeLists.txt (+0/-3)
src/main.cpp (+14/-89)
tests/mocks/Unity/Application/Application.qmltypes (+0/-2)
tests/mocks/Unity/Application/ApplicationDBusAdaptor.cpp (+75/-0)
tests/mocks/Unity/Application/ApplicationDBusAdaptor.h (+43/-0)
tests/mocks/Unity/Application/ApplicationInfo.cpp (+71/-23)
tests/mocks/Unity/Application/ApplicationInfo.h (+22/-9)
tests/mocks/Unity/Application/ApplicationManager.cpp (+60/-31)
tests/mocks/Unity/Application/ApplicationManager.h (+15/-9)
tests/mocks/Unity/Application/CMakeLists.txt (+6/-2)
tests/mocks/Unity/Application/MirSurfaceItem.cpp (+172/-0)
tests/mocks/Unity/Application/MirSurfaceItem.h (+121/-0)
tests/mocks/Unity/Application/SurfaceManager.cpp (+73/-0)
tests/mocks/Unity/Application/SurfaceManager.h (+54/-0)
tests/mocks/Unity/Application/VirtualKeyboard.cpp (+55/-0)
tests/mocks/Unity/Application/VirtualKeyboard.h (+35/-0)
tests/mocks/Unity/Application/plugin.cpp (+16/-9)
tests/qmltests/Dash/Apps/tst_RunningApplicationsGrid.qml (+23/-2)
tests/qmltests/Launcher/tst_Launcher.qml (+11/-2)
tests/qmltests/Panel/tst_ActiveCallHint.qml (+1/-0)
tests/qmltests/Stages/tst_PhoneStage.qml (+9/-56)
tests/qmltests/tst_Shell.qml (+111/-10)
| summary: |
- [qtcomp] Vkb statys above indicators panel + [qtcomp] Vkb status above indicators panel |
| summary: |
- [qtcomp] Vkb status above indicators panel + [QtComp] Vkb status above indicators panel |
| Changed in unity8: | |
| assignee: | nobody → Daniel d'Andrada (dandrader) |
| status: | New → In Progress |
Revision history for this message
| Daniel d'Andrada (dandrader) wrote Re: [QtComp] Vkb status above indicators panel | #1 |
Revision history for this message
| Michael Zanetti (mzanetti) wrote | #2 |
| summary: |
- [QtComp] Vkb status above indicators panel + [QtComp] Vkb stays above indicators panel |
| Changed in unity8: | |
| status: | In Progress → Fix Committed |
| Changed in unity8: | |
| status: | Fix Committed → Fix Released |
| affects: | unity8 → unity8 (Ubuntu) |
To post a comment you must log in.
Caused by the fix for bug 1337908