Open Bug 1904226 Opened 3 months ago Updated 1 month ago

latest update graphical issues/ white boxes

Categories

(Core :: Graphics: WebRender, defect)

Firefox 127
defect

Tracking

()

UNCONFIRMED

People

(Reporter: taylorcarreriddell, Unassigned)

References

Details

(Keywords: stalled)

Attachments

(1 file)

Attached image firefox_xVcLZgv8dt.png

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

Steps to reproduce:

Since latest update as of 2 days ago and on fresh install with or without clean profile.

Device specs:
Device name DESKTOP-3K59PT5
Processor Microsoft SQ1 @ 3.0 GHz 3.00 GHz
Installed RAM 8.00 GB (7.54 GB usable)
Device ID 5530AD7D-6525-4EBE-B9CE-C8F21AE4C81D
Product ID 00342-23746-86434-AAOEM
System type 64-bit operating system, ARM-based processor
Pen and touch Pen and touch support with 10 touch points

Actual results:

Elements on most if not all websites, including this very page become blocked out with white boxes making navigating and comprehension hard if not impossible.
anything with pure white text is invisible.
the elements can change back to normal sometimes by either highlighting , moving the mouse around or even typing but only a portion at times and back to white sometimes too.
funnily enough firefox's inbuilt screenshotting tool does not display it.

Expected results:

The page elements should stay consistent and be readable.

sounds similar to bug 1904190 and bug 1903048.

Component: Untriaged → Graphics: WebRender
Product: Firefox → Core
See Also: → 1904190
See Also: → 1903048

S2, but likely a dupe.

Severity: -- → S2

Reporter: until this is fixed, you can probably work around this by visiting about:config and searching that preference-list for gfx.webrender.software, and toggling it to true. This gets you the software backend for webrender, which means graphical operations will be a bit slower (they won't benefit from GPU acceleration), but Firefox should become usable again.

I'm guessing[1] that this is a Surface Pro X with Adreno graphics hardware (which I think is the only option for Surface Pro X). Reporter, could you confirm that?

It might be useful to document your exact GPU and driver version, as reported by Firefox in about:support (in the "GPU #1" section).

[1] when I google for "Microsoft SQ1" (from comment 0), the first few results are all about Surface Pro X

Flagging as stalled until we get the requested info from the reporter.

Keywords: stalled
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: