stop checking displayport size against max texture size
Categories
(Core :: Panning and Zooming, enhancement)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox95 | --- | fixed |
People
(Reporter: tnikkel, Assigned: tnikkel)
Details
Attachments
(2 files)
|
Assignee | |
Comment 1•3 years ago
|
||
No longer necessary, and it only NS_ASSERTION'd if we failed anyway, and we weren't even checking on mac and android due to the tiling pref.
|
||
Updated•3 years ago
|
|
|
Assignee | |
Comment 2•3 years ago
|
||
The reason that GetDisplayPortForVisibilityTesting was using Drop was because there is a test that sets a 10x zoom and we ran image visibility without updating the displayport base rect (painting would update it), so the returned displayport was based on the much larger base rect. The patches goal was to avoid the assert we removed. Using a displayport that large in that situation for image visibility seems fine because it shouldn't make us decode any more images then were previously already visible.
Depends on D127731
Pushed by tnikkel@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/811ec184b294 Stop checking displayport size against max texture size. r=jrmuizel https://hg.mozilla.org/integration/autoland/rev/2226e24d027d Remove MaxSizeExceededBehaviour from displayport getter options as it is unused. r=botond
|
||
Comment 4•3 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/811ec184b294
https://hg.mozilla.org/mozilla-central/rev/2226e24d027d
Description
•