Sorry, looks like I never followed up on comment 7 - comment 9. Looks like we ended up OK, though, given that we've got WebRender as our only rendering backend now, and the test referenced in comment 6 is passing everywhere too. I'm not sure whether the issue described in comment 0 is still a problem, but given that it was referencing bug 1149222 comment 30 where I had noted "So the bug here may only be possible to expose in XUL", it's probably not a high priority. --> closing this bug as incomplete since we didn't end up with a testcase to demonstrate any actual defect here (and to the extent that a defect remains, it's not especially noteworthy if it's XUL-specific)
Bug 1151016 Comment 10 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Sorry, looks like I never followed up on comment 7 - comment 9. Looks like we ended up OK, though, given that we've got WebRender as our only rendering backend now, and the test referenced in comment 6 is passing everywhere too. I'm not sure whether the issue described in comment 0 is still a problem, but given that it was referencing bug 1149222 comment 30 where I had noted "So the bug here may only be possible to expose in XUL", it's probably not a high priority. --> closing this bug as incomplete since we didn't end up with a testcase to demonstrate any actual defect here (and to the extent that a defect remains, it's not especially noteworthy if it's XUL-specific and hasn't been causing any trouble up to this point).