Closed
Bug 1087175
Opened 10 years ago
Closed 10 years ago
[Midori 2.0][Call] The background color sometimes is not diaplay when press number on the dial
Categories
(Firefox OS Graveyard :: Gaia::Dialer, defect, P2)
Firefox OS Graveyard
Gaia::Dialer
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: sync-1, Unassigned)
Details
Attachments
(2 files)
FFOS2.0 baseline BuildID: 20140916000205 DEFECT DESCRIPTION: The background color sometimes is not diaplay when press number on the dial REPRODUCING PROCEDURES: 1.enter to call 2.press number ->The background color sometimes is not diaplay when press number on the dial-->ko EXPECTED BEHAVIOUR: ko:The background color should always diaplay when press number ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: MEDIUM REPRODUCING RATE: 1/5 For FT PR, Please list reference mobile's behavior:
Comment 3•10 years ago
|
||
Dears, Please see the vedio.
Comment 4•10 years ago
|
||
This looks like a minor performance issue. Do you agree Gabriele?
Flags: needinfo?(gsvelto)
Comment 5•10 years ago
|
||
(In reply to Johan Lorenzo [:jlorenzo] (QA) from comment #4) > This looks like a minor performance issue. Do you agree Gabriele? Yeah, there's not much we can do here. The button color is changed by setting its active property via CSS. When the user taps a button the layout engine will schedule an event to repaint that element as soon as it gets a chance. However, since we're drawing the numbers at the top of the screen which will keep it busy, when the users taps quickly by the time the layout engine can catch up the button will not be pressed anymore and thus the repaint will be discarded. To improve this we'd need to significantly refactor the callscreen CSS and layout to ensure quicker painting but that's not an easy task and hard to justify for such a minor issue.
Flags: needinfo?(gsvelto)
Comment 6•10 years ago
|
||
Per comment 5, the tradeoff doesn't worth it.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•