Status

()

Core
Layout
--
enhancement
7 years ago
3 months ago

People

(Reporter: cjones, Unassigned)

Tracking

(Blocks: 1 bug, {perf, testcase})

Trunk
perf, testcase
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [tech-p3])

Attachments

(1 attachment)

The inchoate plan as I understand so far is, if a -moz-element source is large/interesting enough, ensure that it gets its own layer, then where the -moz-element is used, insert some kind of reference layer into the layer tree that refers to the source layer.  Then at compositing time, we would adjust the source layer somehow at its reference and composite it directly to screen.  That adjustment could probably just be a transform+clip.

Things get a bit interesting if a -moz-element source itself refers to content that includes a -moz-element.  Shouldn't pose too many problems I wouldn't imagine.
Blocks: 790111

Updated

5 years ago
No longer blocks: 790111

Updated

5 years ago
Blocks: 777749
Blocks: 844910
I don't think -moz-element usage is particularly widespread, so for now this is a nice-to-have optimization for content use case.
Whiteboard: [tech-p3]
Created attachment 8373749 [details]
-moz-element test case

Extracted a test case from current experiments with DOM based compositing for Shumway. Having multiple instances of a shape placed on the screen is a frequently used feature in SWF files. Using -moz-element results in pretty poor performance. This should be optimized.
Keywords: perf, testcase
You need to log in before you can comment on or make changes to this bug.