Open Bug 792259 Opened 8 years ago Updated 3 years ago

Using TextureView in LayerView regresses panning performance

Categories

(Firefox for Android :: Toolbar, defect, P3)

All
Android
defect

Tracking

()

Tracking Status
fennec + ---

People

(Reporter: lucasr, Unassigned)

References

(Blocks 1 open bug)

Details

There's definitely a performance hit on panning when we enable rendering in a TextureView.
Blocks: 767980
Removing the blocking ref as bug 767980 can land without this fix.
No longer blocks: 767980
Blocks: 783193
Adding tracking 20 as it blocks a tracking 20 bug.
tracking-fennec: --- → 20+
tracking-fennec: 20+ → +
filter on [mass-p5]
Priority: -- → P5
As per convo with Snorp, this has potential for immense UX wins in terms of better establishing a mental model of this relationship the tab/content has with the tabs tray, and just more intriguing tabs management capabilities overall. 

If we could do this, we would be able to improve our UX in the tabs tray quite a bit.
If we can't get around the performance drop-off, it might be worth considering investigating whether we can switch on-the-fly to enable more complex/synchronised animations?
(In reply to Chris Lord [:cwiiis] from comment #5)
> If we can't get around the performance drop-off, it might be worth
> considering investigating whether we can switch on-the-fly to enable more
> complex/synchronised animations?

Yup, that's my thought too.
You need to log in before you can comment on or make changes to this bug.