Content not displayed on homescreen, emails when disabling low precision painting and transparency

NEW
Unassigned

Status

()

Core
Graphics: Layers
3 years ago
3 years ago

People

(Reporter: gerard, Unassigned)

Tracking

({dogfood, regression})

Trunk
ARM
Gonk (Firefox OS)
dogfood, regression
Points:
---

Firefox Tracking Flags

(tracking-b2g:backlog)

Details

(Reporter)

Description

3 years ago
[Blocking Requested - why for this release]: Major graphic bug

Since a couple of days on master with both my Nexus S and my Flame, I have some content that does not get drawn at several places: homescreen, email.

STR for Homescreen:
 0. Boot device
 1. Scroll homescreen to the bottom

Expected:
 Icons are painted

Actual:
 Some icons are missing and are cut, like if part of the tiles were not rendered.

One need more than 50 apps installed to reproduce this one

STR for email:
 0. Open email client, 
 1. Tap on an account, scroll the list of folders

Expected:
 All folders are visible

Actual:
 The first folders are drawn, then it's all blank gray

This is here since a couple of days.
(Reporter)

Comment 1

3 years ago
On email it also reproduced when displaying content: a long enough email will be drawn partly.
(Reporter)

Updated

3 years ago
Summary: Content not displayed on homescreen, emails → Content not displayed on homescreen, emails when disabling low precision painting/transparency
(Reporter)

Comment 2

3 years ago
It seems to be related to the disabling of low precision painting and transparency.
Summary: Content not displayed on homescreen, emails when disabling low precision painting/transparency → Content not displayed on homescreen, emails when disabling low precision painting and transparency
Could really use more information on the versions, maybe a screen grab, regression range, why the conclusion "it seems to be related to ... low precision painting", etc.
Keywords: regressionwindow-wanted
Oh, wait, are you saying this only shows up when you disable low precision in the developer menu?  I don't think that can be a blocker.
(Reporter)

Comment 5

3 years ago
(In reply to Milan Sreckovic [:milan] from comment #4)
> Oh, wait, are you saying this only shows up when you disable low precision
> in the developer menu?  I don't think that can be a blocker.

Yes. Sorry, I don't have all those infos. I noticed it a couple of days ago, and I know it's still happening when you disable both. Reproduced on Nexus S and Flame for sure, master branch.

I don't know the use of low precision stuff, but if you think we should not block on it, it's your call. I just find it suspicious that disabling those options, we are loosing some content displayed.
Typically we only do regression windows on blocking issues mainly because windows are expensive to conduct. comment 4 is implying that this bug only reproduces when a developer pref is set, so it's arguing to not block on this. If we believe this isn't a blocker, then can we remove this from the blocking list & remove the window request?
Flags: needinfo?(milan)
Understood.  Alexandre has a good point, this could be a bug with the default setting as well, but showing up "better" when we change it.  We'll have to figure that out on the side though, in the meantime, since it currently only reproduces with the developer only setting modified, I'll move it to backlog.  I'm CC-ing Kats & Botond, this is probably of interest.
blocking-b2g: 2.1? → backlog
Flags: needinfo?(milan)
Keywords: regressionwindow-wanted
(Assignee)

Updated

3 years ago
blocking-b2g: backlog → ---
tracking-b2g: --- → backlog
You need to log in before you can comment on or make changes to this bug.