I don't think it's a huge amount of work (maybe a day or two of work), but I'm not sure of the priority of it at the moment. I think what we need to do is: - Restore the functionality removed in #1593154. - Change that functionality so it's only enabled on platforms that don't have the overlapping dirty rect restriction (via renderer options or platform / extension detection). - Add some invalidation test coverage to `test_invalidation.rs` - Do some basic testing on platforms that support this mode before enabling in nightly. It'd be interesting to know how many frames hit this case where the area of the combined dirty rect is significantly more than the area of the individual dirty rects, on real web content. But the time to implement / test that might be just as much as the work to do the implementation above.
Bug 1640712 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I don't think it's a huge amount of work (maybe a day or two of work), but I'm not sure of the priority of it at the moment. I think what we need to do is: - Restore the functionality removed in Bug #1593154. - Change that functionality so it's only enabled on platforms that don't have the overlapping dirty rect restriction (via renderer options or platform / extension detection). - Add some invalidation test coverage to `test_invalidation.rs` - Do some basic testing on platforms that support this mode before enabling in nightly. It'd be interesting to know how many frames hit this case where the area of the combined dirty rect is significantly more than the area of the individual dirty rects, on real web content. But the time to implement / test that might be just as much as the work to do the implementation above.