Quad shaders use a mix of device and layout coordinate spaces
Categories
(Core :: Graphics: WebRender, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox128 | --- | fixed |
People
(Reporter: nical, Assigned: nical)
References
(Blocks 1 open bug)
Details
Attachments
(8 files, 1 obsolete file)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review |
If a quad primitive uses the direct rendering strategy, the shader receives layout-space coordinates and a transform. If the primitive is segmented, however (via tiling or a nine-patch), then for pattern and composite segments the shader receives coordinates in device space and no transform. quad render tasks look like they work with layout space as well.
This causes issues because the pattern is built before the quad rendering strategy and always in layout space. We have to either consistently use layout space coordinates or make it possible to transform patterns and pass a mix of transformed and non-transformed patterns depending on the segment.
Assignee | ||
Comment 1•1 year ago
|
||
This patch mainly extracts the direct/indirect quad segment separation in the scratch buffers from D207657
Updated•1 year ago
|
Assignee | ||
Comment 2•1 year ago
|
||
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 4•1 year ago
|
||
Comment 5•1 year ago
|
||
bugherder |
Assignee | ||
Comment 7•1 year ago
|
||
Assignee | ||
Comment 8•1 year ago
|
||
Not immediately necessary but when cached quads or patterns that read a texture are implemented, There will be opaque segments taking render tasks as input. Currently the code is a bit error prone because some parts of the code advertize a certain behavior that is later overruled. This patch makes things more explicit and flexible.
Comment 9•1 year ago
|
||
bugherder |
Assignee | ||
Comment 10•1 year ago
|
||
Comment 11•1 year ago
|
||
Comment 12•1 year ago
|
||
bugherder |
Comment 13•1 year ago
|
||
Assignee | ||
Comment 14•1 year ago
|
||
Assignee | ||
Comment 15•1 year ago
|
||
Same as https://phabricator.services.mozilla.com/D209622 with a few extra fixes.
Comment 16•11 months ago
|
||
Updated•11 months ago
|
Comment 17•11 months ago
|
||
bugherder |
Updated•11 months ago
|
Comment 18•11 months ago
|
||
Comment 19•11 months ago
|
||
bugherder |
Assignee | ||
Updated•11 months ago
|
Updated•11 months ago
|
Description
•