Closed Bug 899505 Opened 11 years ago Closed 7 years ago

Tuning the performance for IME app switching

Categories

(Firefox OS Graveyard :: Gaia::System::Input Mgmt, defect, P1)

Product:
Firefox OS Graveyard
Component:
Gaia::System::Input Mgmt
Platform:
ARM
Gonk (Firefox OS)
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: rudyl, Unassigned)

References

Details

(Keywords: perf, Whiteboard: [c=effect p= u= s=] [FT:System-Platform], [3rd-party-keyboard] )

+++ This bug was initially created as a clone of Bug #858383 +++ After Bug 858383, we do the integration of the new keyboard manager and 3rd-party keyboard apps. With this change, we might need some extra work to tune the performance for keyboard switching, which covers 2 cases, 1. Switch from one layout of app1 to layout2. 2. Switch from one layout of app1 to another layout of app2.
Keywords: perf
Whiteboard: [c= p= u= s=]
Priority: -- → P1
Whiteboard: [c= p= u= s=] → [c= p= u= s=] [ucid:SystemPlatform1], [FT: System Platform], [Sprint: 3]
Assignee: nobody → gchen
Status: NEW → ASSIGNED
Whiteboard: [c= p= u= s=] [ucid:SystemPlatform1], [FT: System Platform], [Sprint: 3] → [c= p= u= s=] [ucid:SystemPlatform1, FT: System Platform, koi:p1], [Sprint: 3]
Whiteboard: [c= p= u= s=] [ucid:SystemPlatform1, FT: System Platform, koi:p1], [Sprint: 3] → [c= p= u= s=] [ucid:SystemPlatform1, FT: System-Platform, koi:p1], [Sprint: 3]
Whiteboard: [c= p= u= s=] [ucid:SystemPlatform1, FT: System-Platform, koi:p1], [Sprint: 3] → [c= p= u= s=] [ucid:SystemPlatform1, FT:System-Platform, koi:p1], [Sprint: 3]
Change to koi? per discussion with engineers. We will keep the performance turning after 9/16. Not a blocker for v1.2 code complete now
blocking-b2g: koi+ → koi?
Update keyword in white board for the status query more precise
Whiteboard: [c= p= u= s=] [ucid:SystemPlatform1, FT:System-Platform, koi:p1], [Sprint: 3] → [c= p= u= s=] [FT:System-Platform], [Sprint: 3]
fxos-perf triage: minusing from koi. Ivan and team if you feel differently please renominate.
blocking-b2g: koi? → -
Whiteboard: [c= p= u= s=] [FT:System-Platform], [Sprint: 3] → [c= p= u= s=] [FT:System-Platform], [Sprint: 3][perf-reviewed]
blocking-b2g: - → koi?
koi+'ing since Taipei team believes it should be and Gary Chen is assigned for implementation.
blocking-b2g: koi? → koi+
Whiteboard: [c= p= u= s=] [FT:System-Platform], [Sprint: 3][perf-reviewed] → [c=effect p= u= s=] [FT:System-Platform], [Sprint: 3]
Stolen from Gary.
Assignee: gchen → lchang
Move to 1.3 for improvement
blocking-b2g: koi+ → 1.3?
Rudy, could you write down the desire outcome of this bug, maybe a visual effect difference? We cannot block an issue w/o specifics. Thanks.
blocking-b2g: 1.3? → ---
Flags: needinfo?(rlu)
The only concern of this bug should be, how we handle the app switching *visually*, with a animation to slide down the current keyboard app and wait for the new app to launch and then show it up with another transition. Right now, I am not sure how we handle the extreme case, and do some experiments with Gary to clarify this issue.
Flags: needinfo?(rlu)
Whiteboard: [c=effect p= u= s=] [FT:System-Platform], [Sprint: 3] → [c=effect p= u= s=] [FT:System-Platform], [3rd-party-keyboard]
take it back.
Assignee: lchang → gchen
Is this fully implemented? Is there a test case that shows a slow transition for the keyboards? If not, then let's close this bug out.
Flags: needinfo?(rlu)
This is not about the transition used for keyboard showing/hiding, instead it is about when we switch from one keyboard layout to another. We might need to test out different UI behaviors, so that we could decide which way to go. Thanks.
Flags: needinfo?(rlu)
Assignee: gchen → nobody
Component: Gaia::Keyboard → Gaia::System::Input Mgmt
Firefox OS is not being worked on
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.