Closed Bug 1626041 Opened 6 years ago Closed 3 years ago

Antialiasing issue with css transform

Categories

(Core :: Graphics, defect, P3)

74 Branch
defect

Tracking

()

RESOLVED FIXED

People

(Reporter: bugger, Unassigned, NeedInfo)

References

Details

Attachments

(2 files)

Attached image FF.png

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0

Steps to reproduce:

Setting 3 borders and a css transform rotate

Test case: https://jsfiddle.net/kedvqswa/

Actual results:

Before rotating, borders display as a solid white rectangle as it should.
After rotating, a thin pixle line displays dividing the rectangle into two halfs.

Expected results:

Expected results: rectangle should display the same after as before rotation.

I can reproduce on Nightly76.0a1 Windows10 (HWA off or WebRender off).

Status: UNCONFIRMED → NEW
Component: Untriaged → Graphics
Ever confirmed: true
Product: Firefox → Core

This also affects css transform scale when transform-origin is set.

Test case 2: https://jsfiddle.net/0gd3tvzj/

Looks like the primitive edge flags are broken in WR. Adding Glenn and Nical.
This is technically P3, but one of those things that may be very visible. We should get that sooner.

Priority: -- → P3

Please attached about:support output

Flags: needinfo?(bugger)
Attached file about:support

Thank you!
Interesting, so this is non-WR.
Could you try enabling WR in "about:support", the "gfx.webrender.all" property, restarting the browser, and seeing if it's fixed? We are trying to roll out WebRender everywhere.

Yes, setting "gfx.webrender.all" true fixes the issue

"adapterDescription": "Intel(R) HD Graphics 520",
"adapterVendorID": "0x8086",
"adapterDeviceID": "0x1916",

"driverVersion": "20.19.15.4463",
"driverDate": "5-25-2016",

"Display0": "1366x768@60Hz "

If the driver version were at least 25.20.100.6472, WebRender would be enabled by default with upcoming Firefox 76 (bug 1615049).

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)

Severity: normal → S3

WR shipped everywhere.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: