If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Using TextureView in LayerView regresses panning performance

NEW
Unassigned

Status

()

Firefox for Android
Graphics, Panning and Zooming
P3
normal
5 years ago
a year ago

People

(Reporter: lucasr, Unassigned)

Tracking

(Blocks: 1 bug)

Trunk
All
Android
Points:
---

Firefox Tracking Flags

(fennec+)

Details

(Reporter)

Description

5 years ago
There's definitely a performance hit on panning when we enable rendering in a TextureView.
(Reporter)

Updated

5 years ago
Blocks: 767980
(Reporter)

Comment 1

5 years ago
Removing the blocking ref as bug 767980 can land without this fix.
No longer blocks: 767980
(Reporter)

Updated

5 years ago
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.

Comment 5

3 years ago
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.
Priority: P5 → P3
You need to log in before you can comment on or make changes to this bug.