Closed Bug 1133966 Opened 10 years ago Closed 10 years ago

Flame: Settings -> Sound -> Manage Tones window transition seems broken

Categories

(Core :: Graphics: Layers, defect)

All
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1137203
blocking-b2g 2.2+
Tracking Status
b2g-v2.2 --- affected
b2g-master --- affected

People

(Reporter: njpark, Assigned: BenWa)

References

Details

(Keywords: regression)

Attachments

(1 file)

STR: Open Settings -> Sound -> Manage Tones menu Actual: The window transition seems broken, and it is different from Bug 1127877. Expected: The window transition is normal Video Link: https://www.youtube.com/watch?v=qssUv6eaUII Version Info: 2.2 No-Jun-MacBook-Pro:B2G-flash-tool mozilla$ ./check_versions.sh Gaia-Rev ea64caf6d4ab03fc4472eca9f41f20d651d55fa9 Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/78d823f7be4c Build-ID 20150217002515 Version 37.0a2 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20150217.040742 FW-Date Tue Feb 17 04:07:53 EST 2015 Bootloader L1TC000118D0 3.0 Gaia-Rev ae02fbdeae77b2002cebe33c61aedeee4b9439fd Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/4bb425001d8a Build-ID 20150217074221 Version 38.0a1 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20150217.111839 FW-Date Tue Feb 17 11:18:50 EST 2015 Bootloader L1TC000118D0
ni?ing milan for possible graphics bug. Nominating for 2.2 since the transition is quite noticeably wrong.
blocking-b2g: --- → 2.2?
Flags: needinfo?(milan)
Component: Gaia::Settings → Graphics: Layers
OS: Mac OS X → Gonk (Firefox OS)
Product: Firefox OS → Core
Hardware: x86 → All
This goes away if bug 1121871 is backed out.
Blocks: 1121871
Assignee: nobody → bgirard
Flags: needinfo?(milan)
Keywords: regression
Triage is blocking because this is a regression.
blocking-b2g: 2.2? → 2.2+
I can still reproduce this with bug 1134762 landed (which cleaned up bug 1121871). Investigating.
It is related to low-res painting. Not related to intermediate surface recycling (turning it off makes the glitches worse cause we repaint it every frame).
Attached patch work aroundSplinter Review
Ok kats is correct. The problem is we only draw the critical display port. With OMTA we have to draw everything.
The animation is set on the parent container layer. Going to try to disable the critical display port code if there's an animation on an ancestor layer.
The problem in the work around I found will be addressed in bug 1137203.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: