Closed Bug 1075271 Opened 11 years ago Closed 10 years ago

[Email] Low precision painting option will blur text during CSS transitions

Categories

(Core :: Graphics: Layers, defect, P2)

ARM
Gonk (Firefox OS)
defect

Tracking

()

RESOLVED WORKSFORME
blocking-b2g -
Tracking Status
b2g-v2.1 --- affected
b2g-v2.2 --- unaffected

People

(Reporter: tchung, Unassigned)

References

()

Details

[Blocking Requested - why for this release]: Nominating because i think low-precision option is turned ON by default for 2.1. ni? Graphics team if they can confirm or not. When i enable low-precision painting option, the text in CSS transitions tends to blur on display. Disabling it will be smooth again. See screencast. : http://youtu.be/yMZlsk2HJF8 Repro 1) install 2.1 aurora build on Flame Kitkat 2) in Settings > Developer tool, enable Low-precision painting option Gaia-Rev a00d102abfe8ae15c4fd14771efa2335c6d3b8d9 Gecko-Rev https://hg.mozilla.org/releases/mozilla-aurora/rev/cde28bd9a285 Build-ID 20140930000203 Version 34.0a2 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20140930.041115 FW-Date Tue Sep 30 04:11:26 EDT 2014 Bootloader L1TC10011800 2) launch email App, and add two different email accounts 3) goto to accounts dropdown, and tap the arrow to switch between accounts 4) Observe the text as the CSS transitions happen during the DOM redrawing the folders. Verify the blurriness of the text. Expected: - with low-precision painting on, the CSS transitions is blurry text Actual: - smooth text.
Flags: needinfo?(milan)
Right - the text is "bold and blurry" because it's low precision, scaled up. We hit the low precision tiles because we don't have time to paint them in high precision. I assume changing accounts is an expensive operation, so it takes a while to get the data, and then we have to redraw everything? I'm assuming E-mail DOM changes are as optimal as can be, and there are no help from that side? Otherwise, I don't think we're setup to dynamically disable low precision tiling just during transitions, or anything like that, right Kats?
Flags: needinfo?(milan)
From the video linked in comment 0 that actually doesn't look like low-precision tiling to me. For one thing the opacity looks like it's still at 100% which shouldn't be the case with low-precision tiling. tchung, it wasn't in the video but can you confirm that it doesn't appear blurry when you have low-precision tiling disabled? The expectation is that we only draw low-precision when we would be checkerboarding instead, so if you see sharp content with low-precision disabled, then either we have a few different bugs going on in the low-precision code, or this is something else entirely.
Flags: needinfo?(tchung)
(In reply to Kartikaya Gupta (email:kats@mozilla.com) from comment #2) > From the video linked in comment 0 that actually doesn't look like > low-precision tiling to me. For one thing the opacity looks like it's still > at 100% which shouldn't be the case with low-precision tiling. tchung, it > wasn't in the video but can you confirm that it doesn't appear blurry when > you have low-precision tiling disabled? The expectation is that we only draw > low-precision when we would be checkerboarding instead, so if you see sharp > content with low-precision disabled, then either we have a few different > bugs going on in the low-precision code, or this is something else entirely. darn, i thought i replied here, but my bugzilla comment didnt stick. here's a video of both on and off setting. http://youtu.be/By-1Rq5kOi0 .
Flags: needinfo?(tchung)
Thanks for the video. It does appear to be related to low-res tiling; perhaps we are generating two layers with the same content and one gets drawn in low-res on top of the other, so the opacity change doesn't show up? It will require some investigation I think.
Component: Gaia::E-Mail → Graphics: Layers
Product: Firefox OS → Core
There is no low-precision tiling option in develop mode in 2.2.
Priority: -- → P2
i can't duplicate problem in my Flame 2.1. ------------ Gaia e9b9ee15eded2671656efbc40f8437ae8a61d55c Gecko https://hg.mozilla.org/releases/mozilla-aurora/rev/49bd5bad84d2 BuildID 20141007170148 Version 34.0a2
Flags: needinfo?(tchung)
(In reply to Bobby Chien [:bchien] from comment #6) > i can't duplicate problem in my Flame 2.1. > > ------------ > > Gaia e9b9ee15eded2671656efbc40f8437ae8a61d55c > Gecko https://hg.mozilla.org/releases/mozilla-aurora/rev/49bd5bad84d2 > BuildID 20141007170148 > Version 34.0a2 I'm not sure what to tell you. my STR in comment 3 was against a build yesterday, Oct 10th. I can try and see if there's anything in logcat rendering, but essentially I had 2 email accounts (gmail and mozilla), and you can see from the video that it blurs while redrawing. What information do you need to resolve this? I also dont know yet where else this is reproducing, but i'll try to look and report back if there's other places like this.
Flags: needinfo?(tchung)
Adding qawanted to see if they can reproduce the issue.
Keywords: qawanted
I was not able to reproduce this bug with the build on Comment 0: Environmental Variables: Device: Flame 2.1 (shallow & full flash) BuildID: 20140930000203 Gaia: a00d102abfe8ae15c4fd14771efa2335c6d3b8d9 Gecko: cde28bd9a285 Version: 34.0a2 (2.1) Firmware Version: V180 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Repro rate: 0/10 The text did not blur during CSS transitions with Low-precision painting on. --------------------------------------------------- Leaving qawanted keyword for others to try.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
I was unable to reproduce this issue with the latest aurora eng build or the reporters build. Environmental Variables: Device: 2.1 BuildID: 20141011150624 Gaia: f5d4ff60ffed8961f7d0380ada9d0facfdfd56b1 Gecko: e96a7a4f3bbe Version: 34.0a2 (2.1) Firmware: V180 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Device: Flame 2.1 BuildID: 20140930000203 Gaia: a00d102abfe8ae15c4fd14771efa2335c6d3b8d9 Gecko: cde28bd9a285 Gonk: 52c909e821d107d414f851e267dedcd7aae2cebf Version: 34.0a2 (2.1) Firmware: V180 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Result: the text never appears to be blurry. leaving qawanted tag for others to check.
This issue did not reproduce on the latest aurora engineering build or the reporters build. Actual results: The text never becomes blurry. Environmental Variables (shallow flash): Device: Flame 2.1 BuildID: 20141011150624 Gaia: f5d4ff60ffed8961f7d0380ada9d0facfdfd56b1 Gecko: e96a7a4f3bbe Version: 34.0a2 (2.1) Firmware Version: v180 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Environmental Variables (shallow flash): Device: Flame 2.1 BuildID: 20140930000203 Gaia: a00d102abfe8ae15c4fd14771efa2335c6d3b8d9 Gecko: cde28bd9a285 Version: 34.0a2 (2.1) Firmware Version: v180 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Keywords: qawanted
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
Hi Tony, could you check whether you can still see this issue? thanks!
Flags: needinfo?(tchung)
This still reproduces for me on today's 2.1 build. are you guys at setting up at least 2 accounts? again, when the low-precision painting box is checked, the text is blurry. Let me know if someone needs my device to debug, or my profile if that helps. Gaia-Rev 379ea4c9dd6d3f8ca2f79ce59c15f6afe6e557c3 Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/4853208cb48a Build-ID 20141015001201 Version 34.0 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20141011.032649 FW-Date Sat Oct 11 03:26:59 EDT 2014 Bootloader L1TC00011840
Flags: needinfo?(tchung)
(In reply to Tony Chung [:tchung] from comment #13) > This still reproduces for me on today's 2.1 build. are you guys at setting > up at least 2 accounts? again, when the low-precision painting box is > checked, the text is blurry. > > Let me know if someone needs my device to debug, or my profile if that helps. > > Gaia-Rev 379ea4c9dd6d3f8ca2f79ce59c15f6afe6e557c3 > Gecko-Rev > https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/4853208cb48a > Build-ID 20141015001201 > Version 34.0 > Device-Name flame > FW-Release 4.4.2 > FW-Incremental eng.cltbld.20141011.032649 > FW-Date Sat Oct 11 03:26:59 EDT 2014 > Bootloader L1TC00011840 I try to do it again. still can't reproduce it. I'm not sure what wrong between our flames. video attached: http://youtu.be/CK8KRH3qU0I Gaia-Rev 477a9e61c3edf12f32a62a19d329cd277202cc6b Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/67573e422a0f Build-ID 20141015161201 Version 34.0 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20141007.202947 FW-Date Tue Oct 7 20:29:58 EDT 2014 Bootloader L1TC00011840 is it possible caused by firmware version?
A few of us in triage talked about this and decided that it's not great but that it doesn't meet the blocker criteria. Obviously feel free to re-nom and add your thoughts if you disagree :)
blocking-b2g: 2.1? → -
Please reopen this if issue could be reproduced.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.