Closed Bug 1840281 Opened 1 year ago Closed 1 year ago

Correctness bug on StackOverflow.com

Categories

(Core :: Graphics: WebRender, defect, P3)

Firefox 116
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: gfxreporter, Unassigned)

References

()

Details

(Keywords: correctness)

Steps to reproduce:

  1. Open TAB1: https://stackoverflow.com/questions
  2. Right click on question link and choose "Open link in a new tab" so it opens in TAB2
  3. Scroll down while in TAB1
  4. Go to TAB2

(My browser window size width=1000, height=900)

Actual results:

Huge purple rectangle in the left side panel

Expected results:

No huge purple rectangle in the left side panel

This was tested on Firefox 116.0a1
Build ID 20230624211408
Ubuntu.

Confirmed with WebRender Software, I don't have access to a machine where I can run normal WebRender to test if it reproduces there.

Component: Untriaged → Graphics: WebRender
Keywords: correctness
Product: Firefox → Core

Note that the purple rectangle is due to the background of about:privatebrowsing (this was tested on a private browsing window).

I will test the STR on my Ubuntu system as well to see if I can reproduce, but for the moment, could you please attach the output of your about:support to this report when you get a chance?

Flags: needinfo?(gfxreporter)

Just tested with Ubuntu 22.04.2 LTS 64-bit using Fx116.0a1 (20230627094831) using WR (accelerated). The STR does not produce a purple rectangle.

Turned off WR and tried again with software only (SW/WR). Same result: no visual artifacting.

Severity: -- → S3
Priority: -- → P3

I believe there was a sitewide change on StackOverflow and other StackExchange websites that made it very hard to reproduce this bug even in older versions of Firefox (I was only able to reproduce it once with many trials). I will open a new bug if I find a reliable way to reproduce it.

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → INVALID
Flags: needinfo?(gfxreporter)
No longer blocks: wr-correctness
You need to log in before you can comment on or make changes to this bug.