Closed
Bug 1025946
Opened 10 years ago
Closed 10 years ago
Line shows blurred message when opening app
Categories
(Core :: Panning and Zooming, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1026756
blocking-b2g | 2.0+ |
People
(Reporter: bkelly, Unassigned)
References
Details
(Keywords: regression, Whiteboard: [dogfood2.0])
Attachments
(1 file)
(deleted),
image/png
|
Details |
When I open the Line app on my v2.0 flame device it seems to show my message history in high res, but when it adds the last message received it remains blurred out. See the attached screenshot.
If I scroll the view slightly it repaints in high res.
I assume this is related to our progressive blurring code on scrolling.
Not sure if its relevant, but Line does not have a meta viewport tag.
The screenshot is from the aurora pvt nightly on 6/16.
Reporter | ||
Comment 1•10 years ago
|
||
You can also see from the screenshot that the blurred text is actually duplicated from the high res text. Some kind of race condition?
Updated•10 years ago
|
blocking-b2g: 2.0? → 2.0+
Comment 3•10 years ago
|
||
Ben, can you check to see if this still happens now that 1026756 is landed?
Flags: needinfo?(bkelly)
Reporter | ||
Comment 4•10 years ago
|
||
My dogfood device is tracking v2.0, so can we get this uplifted first?
Flags: needinfo?(bkelly)
Comment 5•10 years ago
|
||
While waiting for that, chances are this is low res tiling which we're (for some reason :) tracking as APZ component...
Component: Graphics → Panning and Zooming
Comment 6•10 years ago
|
||
Bug 1026756 was uplifted yesterday and should be in the latest 2.0 nightly, I think. Bug 1024126 also fixes similar issues and is still pending uplift. Hopefully if it's not fixed yet on 2.0 it will be once bug 1024126 is uplifted.
Depends on: 1024126
Reporter | ||
Comment 7•10 years ago
|
||
Seems fixed. Various other corruption while scrolling line seems to be fixed as well with the latest nightly. Thanks!
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 8•10 years ago
|
||
Great, thanks!
You need to log in
before you can comment on or make changes to this bug.
Description
•