(In reply to Daniel Bodea [:danibodea] from comment #5) > This issue no longer occurs in the latest Nightly v140.0a1 from 2025-05-07. > According to my mozregression investigation on Windows 10, the issue was fixed in bug 1963424. I think you mean "this was fixed by a pushlog range that includes bug 1963424". For me at least, bug 1963424 was the tipmost commit in the fix range (the one I linked in comment 4) -- but bug 1963424 is not itself the fix. Per comment 4, bug 1964293 (related to background painting) seems like the most likely thing to have fixed this in the fix-range, so let's close this as FIXED by that bug.
Bug 1965005 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Daniel Bodea [:danibodea] from comment #5) > This issue no longer occurs in the latest Nightly v140.0a1 from 2025-05-07. > According to my mozregression investigation on Windows 10, the issue was fixed in bug 1963424. I think you mean "this was fixed by a pushlog range that includes bug 1963424". For me at least, bug 1963424 was the first commit in the fix range (the one I linked in comment 4) (and its backout was the last commit in that fix range). But bug 1963424 is not itself the fix. Per comment 4, bug 1964293 (related to background painting) seems like the most likely thing to have fixed this in the fix-range, so let's close this as FIXED by that bug.