Closed Bug 1676347 Opened 4 years ago Closed 4 years ago

The Webrender feature's status in about:support is not "available by user: Qualified enabled pref" when gfx.webrender.force-disabled is set to "false"

Categories

(Core :: Graphics: WebRender, defect)

Firefox 84
ARM64
Android
defect

Tracking

()

RESOLVED INVALID
Tracking Status
firefox84 --- affected

People

(Reporter: mlobontiuroman, Unassigned)

References

Details

Attachments

(1 file)

Attached image webrender.png

STR:

  1. Open Firefox Nightly with a fresh profile.
  2. Go to about:config, search for gfx.webrender.force-disabled, and turn it to "true".
  3. Restart the browser and check about:support.
  4. Go back to about:config, and set the gfx.webrender.force-disabled to "false".
  5. Restart the browser and check about:support.

Expected results:
After step 3, the WebRender feature has the following status:
"disabled by user: User force-disabled WR".
After step 4, the WebRender feature has the following status:
"available by user: Qualified enabled pref".

Actual results:
After step 3, the WebRender feature has the following status:
"disabled by user: User force-disabled WR".
After step 5, the WebRender feature has the following status:
"available by default".

Environment:
Device: Samsung Galaxy Note 8 (Android 9)
Version: Firefox Nightly 11/10 build #2015774763 with GV 84.0a1

Webrender is supposed to be enabled by default on this device. (If it's the version with the Mali GPU then on nightly only, if its the version with the Adreno GPU then on all channels.)

So is this not the correct behaviour?

Andrew, do you know what the status string should say in this case?

Flags: needinfo?(aosmond)

We've tested with Samsung Galaxy Note 8 (Android 9) - SM-G950F Mali G71, and Samsung Galaxy S9 (Android 9) - SM-G960F Mali G72, both Mali-G devices, both Mali-G devices.
I'm not sure which of the status the feature should have: "available by default" or the "available by user: Qualified enabled pref".

I expect to see "available by default" as reported. We inverted the logic in bug 1668360. It should work the same as before.

Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(aosmond)
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: