Closed
Bug 988591
Opened 10 years ago
Closed 10 years ago
Touch events fail on Tarako
Categories
(Firefox OS Graveyard :: Performance, defect, P4)
Tracking
(blocking-b2g:-, b2g-v1.3T affected)
Tracking | Status | |
---|---|---|
b2g-v1.3T | --- | affected |
People
(Reporter: nfong, Assigned: Harald)
References
()
Details
(Keywords: perf, Whiteboard: [c= p= s=2014.07.18.t u=tarako] )
Seems correlated to app performance. Example App 1: Line APP ID 477640 Steps to reproduce - Open Marketplace, search for app, install/launch, start chatting, observe keyboard response. Example App 2: Duck Shooting APP ID 404519 Steps to reproduce - Open Marketplace, search for app, install and launch, play game and observe responsiveness.
Updated•10 years ago
|
Comment 1•10 years ago
|
||
batch update: 1.3T? so we can get more eyes into these marketplace related bugs
blocking-b2g: --- → 1.3T?
Comment 2•10 years ago
|
||
Thomas, this can be used as a meta bug, if you can file bug against specific app with videos, that will help the team better. Most likely we will need to remove the app from the marketplace
blocking-b2g: 1.3T? → -
![]() |
||
Updated•10 years ago
|
status-b2g-v1.3T:
--- → affected
Updated•10 years ago
|
Whiteboard: [c= p= s= u=tarako]
Updated•10 years ago
|
Priority: -- → P2
Comment 3•10 years ago
|
||
Setting these to P4 priority since they're not meant to be acted on but discussed. Our performance team is actively troubleshooting and fixing critical Tarako performance issues affecting core applications. You can see what we're working on via our scrum views at: https://scrumbu.gs/p/fxos-perf/
Status: NEW → ASSIGNED
Priority: P2 → P4
Assignee | ||
Comment 4•10 years ago
|
||
This is fixed on latest builds with apps that Marketplace vetted to run on Tarako.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Whiteboard: [c= p= s= u=tarako] → [c= p= s=2014.07.18.t u=tarako]
Updated•10 years ago
|
Target Milestone: --- → 2.0 S6 (18july)
You need to log in
before you can comment on or make changes to this bug.
Description
•