Currently the transition it's horrible in SMS App. We are going to restore the previous handling of transitions that it's smooth and reliable until Platform will be ready.
For me it should be considered bb+ due to the user experience it's not the best with a 'flickering' between transitions. This code could be reverted once the platform will be working with this type of transitions without flickering.
-moz-element has some very bad implications for the keyboard. I'm strongly against this hack.
In this case I've tested the Keyboard and I've not realized about any big impact (I know that in other apps the impact of moz-element & Keyboard it's so bad, but this seems not be the case). However, as it's said in the bug, it's about restoring a workaround until the platform will be working in a right way with this type of animation, so we could remove it once there will be no 'flickering'. In this case we should analyze as a trade-off for V1, due to the user experience with this patch applied it's better than without it.
Hi Vivien, Is there any serious drawback for applying -moz-element under the keyboard(rendering broken or performance decreasing)? BTW, if we can apply snapshot only for animation and hide it when transition end, could it be safer to use -moz-element in the app?
We will wait for platform.
blocking-basecamp: ? → -
Updating the name of this bug. It's related to 827382, so this one should be bb+ as well for being consistent.
Summary: [SMS] Restored transitions until platform will be ready → [SMS] Fix transitions without flickering
blocking-basecamp: ? → +
Priority: -- → P3
Target Milestone: --- → B2G C4 (2jan on)
Comment on attachment 700415 [details] PR https://github.com/mozilla-b2g/gaia/commit/86549ba5af5de93302648a325ee75f1543459bac
Attachment #700415 - Flags: review?(21) → review+
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.