Closed Bug 1830588 Opened 2 years ago Closed 1 years ago

Graphical error on animated box

Categories

(Core :: Graphics: WebRender, defect)

Firefox 114
x86_64
Linux
defect

Tracking

()

RESOLVED FIXED
115 Branch
Tracking Status
firefox-esr102 --- unaffected
firefox-esr115 --- disabled
firefox112 --- unaffected
firefox113 --- unaffected
firefox114 --- disabled
firefox115 --- disabled
firefox116 --- fixed

People

(Reporter: u693231, Assigned: gw)

References

(Regressed 3 open bugs, Regression)

Details

(Keywords: correctness, nightly-community, regression)

Attachments

(2 files)

Steps to reproduce:

hello,
we are receiving reports from users that there is a graphical problem in the clipboard2file extension in firefox nightly that is not present in other versions.

to see the issue for yourself, please go to https://addons.mozilla.org/en-US/firefox/addon/clipboard2file/ and install the extension (following all instructions on the page), then copy an image to the clipboard and try to upload it to a website like imgur, google drive, etc

Actual results:

there is a line on the side of the box

Expected results:

the line should not present as it is not intended

Attached video bug.mp4
Component: Untriaged → Graphics: WebRender
OS: Unspecified → Linux
Product: Firefox → Core
Hardware: Unspecified → x86_64

Thanks for the report! Confirmed on KDE Wayland, Debian Testing, Intel.
It's like an additional 1px border at the right & bottom for a part of a second.

Install addon, go to Google Images tab, copy google logo, click to upload file, press escape, click to upload file, etc.
mozregression --good 2023-02-01 --bad 2023-04-29 --pref dom.events.asyncClipboard.clipboardItem:true -a https://addons.mozilla.org/en-US/firefox/addon/clipboard2file/ -a https://www.google.com/imghp

16:33.35 INFO: Last good revision: dccf044ce33a90816e6a0da2fec9a5d7d05b5924
16:33.35 INFO: First bad revision: 1c58e8743220c7cab1ee952fa3d3a5ba046575cc
16:33.35 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=dccf044ce33a90816e6a0da2fec9a5d7d05b5924&tochange=1c58e8743220c7cab1ee952fa3d3a5ba046575cc

1c58e8743220c7cab1ee952fa3d3a5ba046575cc Glenn Watson — Bug 1823578 - Add new clip-mask rendering path r=gfx-reviewers,ahale

Status: UNCONFIRMED → NEW
Has STR: --- → yes
Ever confirmed: true
Flags: needinfo?(gwatson)
Regressed by: 1823578

This should be temporarily resolved when bug #1830691 lands. I'll work on a proper fix for this before re-enabling the new clip-mask path.

Depends on: 1830691
Flags: needinfo?(gwatson)
Assignee: nobody → gwatson
Severity: -- → S2
Severity: S2 → S3

Set release status flags based on info from the regressing bug 1823578

I can see the bug in the referenced video. However, when I re-enable the new clip-mask path I can't observe the bug locally.

I'm not sure if it's been resolved by some other change, or if the bug only reproduces under certain scenarios, or if I'm just not looking closely enough.

I pushed a try build to https://treeherder.mozilla.org/jobs?repo=try&revision=66296cc9b88936a39700f6fd3382be54b6a8c82a with the new path enabled. Would it be possible for you to locally test the artifacts from that, when they're built, and see if you can still observe the bug?

Flags: needinfo?(kekvord)

hello,
yes we can observe the bug locally (downloaded file named target.tar.bz2)

Flags: needinfo?(kekvord)

Thanks for confirming, I can also reproduce it locally now.

Also add a test and re-enable the new clip-mask code paths.

The attached patch fixes this problem for me locally. If you'd like to verify yourself, there is a try run with the patch applied available at [1]. Otherwise, it should be in nightly within the next 2-3 days.

[1] https://treeherder.mozilla.org/jobs?repo=try&revision=1583625dd888b86c2886d9571cd766721ce250da

Pushed by gwatson@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/928b0d1a27d5 Fix clip on fractional composite prims r=gfx-reviewers,lsalzman
Status: NEW → RESOLVED
Closed: 1 years ago
Resolution: --- → FIXED
Target Milestone: --- → 115 Branch
Regressions: 1836052
Regressions: 1839309
Regressions: 1840229

I discussed on matrix with Donal that the least risky option for this release will likely be to back out 1836693, 1836052 and then 1830588 (this bug) from beta. I've checked that these revert cleanly on beta, and submitted a try run:

https://treeherder.mozilla.org/jobs?repo=try&revision=b8b3e56c4f51bef9610b3fa7ea950982cbe5e54b

I'll update this comment with the results of that try run, but I expect it should be a safe change.

Flags: needinfo?(dmeehan)

Donal, confirming that the try run above looks good to me - so it should be fine to apply those 3 back outs to beta, thanks.

I tried reproducing on Ubuntu 20.04 and Win10 using FF build 114.0a1(20230428092401), but it did not reproduce.
Can you please confirm the fix on latest Beta 115.0b9(link https://archive.mozilla.org/pub/firefox/candidates/115.0b9-candidates/build1/win64/en-US/). Thank you.

Flags: needinfo?(kekvord)

https://hg.mozilla.org/releases/mozilla-release/rev/fa7043f1c4a2
Backed out changeset 928b0d1a27d5 (bug 1830588) with Bug 1836052 and Bug 1836693 for causing regressions

Flags: needinfo?(dmeehan)
Regressions: 1841224
Regressions: 1845184
Regressions: 1849452
Regressions: 1849456
Flags: needinfo?(u693231)
Regressions: 1867056
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: