811844 - Weird background when hiding Cost Control settings

Status: RESOLVED FIXED

(Firefox OS Graveyard :: General, defect, P4)

Description

[Salvador de la Puente González [:salva]]

Attachment: This patch prevent the blank background effect

How to reproduce:
1. Open Cost Control application
2. Tap on the gear to open settings
3. Tap on Done to hide settings

Expected:
Settings smoothly goes down and discover the background view

Currently:
Settings goes down discovering a blank screen that suddenly, disappears.

Comment 1

[Salvador de la Puente González [:salva]]

See the patch attached to see how rare is this bug.

Comment 2

[Kai-Chih Hu [:khu]]

Can you provide video file or image file for this issue? Thanks.

Comment 3

[Kai-Chih Hu [:khu]]

Can you provide video file or image file for this issue? Thanks.

Comment 4

[Salvador de la Puente González [:salva]]

Excuse me. Here is a video:
http://www.youtube.com/watch?v=CLtmXrNF9Tk

Comment 5

[Jason Smith [:jsmith]]

blocking- - this is cleaning up a transition.

Comment 6

[Salvador de la Puente González [:salva]]

What is that? Have you seen how it is solved? I think this is a bug in the platform.

Comment 7

[Salvador de la Puente González [:salva]]

May be you have not seen the patch but the solution is to turn the iframe's opacity to 99%. Why this is happening when the iframe is almost visible and not when it is completely opaque?

This is why I think it is a platform bug.

Comment 8

[Salvador de la Puente González [:salva]]

May be you have not seen the patch but the solution is to turn the iframe's opacity to 99%. Why this is happening when the iframe is almost visible and not when it is completely opaque?

This is why I think it is a platform bug.

Comment 9

[Patryk Adamczyk [:patryk] UX]

Looks like a performance bug, as the background is not being drawn fast enough.

Comment 10

[Salvador de la Puente González [:salva]]

Ok, could it be with a opacity of .99% the background is always being repainted. Thanks for the clues.

Comment 11

[Jet Villegas (inactive)]

Changing the opacity affects changes how we retain Layers for the background graphics. Always retaining Layers will affect memory usage and may not be desirable in this case.

Comment 12

[Andrew Overholt [:overholt]]

This would be good to fix but we can't block on it.  Marking as a "soft blocker" (P4/blocking-).

Comment 13

[Salvador de la Puente González [:salva]]

The solution patch will land when fixing bug #834696

I've used the following schema to do transitions. The view has the following CSS rules:

.view {
 /* non related rules */
 transition: transform .3s ease;
}

And when I want to move it to the bottom I use:

.view[data-viewport="bottom"] {
  transform: translateY(100%);
}

Then I set or unset the data-viewport property. Setting it, causes the view to be moved to the bottom. Removing it causes the view to return to the original position.

For some reason, when setting the data-viewport to bottom, those behind the view is temporally covered by this strange blank overlay for a 100ms and then disappear. I don't know why but If I change the default position rule to:

.view {
  /* non related rules */
  transform: translate(0, 0); /* this has been explicitly set */
  transition: transform .3s ease;
}

Comment 14

[Salvador de la Puente González [:salva]]

If I change the default position rule to:

.view {
  /* non related rules */
  transform: translate(0, 0); /* this has been explicitly set */
  transition: transform .3s ease;
}

It is solved!

(I don't know what happen with the previous commentary)