Open
Bug 904304
Opened 11 years ago
Updated 2 years ago
Firefox transform3D CSS appears broken when there are large amount of elements with transform3D present on the page.
Categories
(Core :: Layout, defect)
Tracking
()
NEW
People
(Reporter: thesilentimp, Unassigned)
References
Details
Attachments
(4 files)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.95 Safari/537.36
Steps to reproduce:
Create large amount of elements with 3D Transformation applied.
Actual results:
Wrong visibility calculation. Elements cover each other in wrong order.
Expected results:
Right visibility calculation.
Reporter | ||
Comment 1•11 years ago
|
||
problem is common for all FF versions
Updated•11 years ago
|
Component: Untriaged → Layout
OS: Mac OS X → All
Product: Firefox → Core
Updated•11 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Reporter | ||
Comment 2•11 years ago
|
||
Reporter | ||
Comment 3•11 years ago
|
||
Reporter | ||
Comment 4•11 years ago
|
||
Updated•11 years ago
|
Flags: needinfo?(roc)
I assume this is just the lack of plane splitting. Currently we have some heuristics for z-ordering 3D transformed elements that don't always work. I.e., bug 689498.
Flags: needinfo?(roc)
Comment 6•9 years ago
|
||
In addition to the plane splitting being required for correct rendering in many cases, there is currently a hard-coded limit to the number of layers that will be sorted:
https://dxr.mozilla.org/mozilla-central/source/gfx/layers/LayerSorter.cpp?from=LayerSorter.cpp&case=true#236
This is currently set to 100. When the layer sorting is fixed, this limit will be bumped up to a more reasonable ceiling that is less likely to be hit.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•