Closed Bug 1442979 Opened 7 years ago Closed 4 years ago

Provide "layers.mlgpu.force-enabled" preference in about:config to force enable "Advanced Layers"

Categories

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

Product:
Core
Component:
Graphics: Layers
Version:
57 Branch
Platform:
x86_64
Windows 7
Type:
defect

Tracking

()

Status:
VERIFIED INVALID
Tracking Flags:
Tracking Status
firefox-esr52 --- unaffected
firefox-esr60 --- wontfix
firefox58 --- wontfix
firefox59 --- wontfix
firefox60 --- wontfix
firefox61 --- wontfix
firefox62 --- wontfix
firefox63 --- wontfix
firefox64 --- wontfix
firefox65 --- wontfix
firefox66 --- wontfix
firefox67 --- wontfix
firefox67.0.1 --- wontfix
firefox68 --- wontfix
firefox69 --- wontfix

People

(Reporter: Virtual, Assigned: bas.schouten)

References

Details

(Keywords: nightly-community, Whiteboard: [gfx-noted])

In about:config these preferences are set as: > layers.mlgpu.sanity-test-failed = false > layers.mlgpu.enable-on-windows7 = true > layers.mlgpu.enabled = true and in about:support under Graphics section under Decision Log > ADVANCED_LAYERS > available by user: Enabled for Windows 7 via user-preference > Blocklisted due to known issues; bug 1419264 So please provide "layers.mlgpu.force-enabled" preference in about:config to force enable "Advanced Layers" for testing, diagnosing and troubleshooting proposes, as when bug #1419264 landed and blocked "Advanced Layers", there is no possibility to force enable "Advanced Layers" and omit blacklist.
Has Regression Range: --- → irrelevant
Has STR: --- → irrelevant
Assignee: nobody → bas
Flags: needinfo?(bas)
Whiteboard: [gfx-noted]
Found a way: SET MOZ_GFX_SPOOF_DRIVER_VERSION=23.21.13.8541 "Path to firefox" in a .bat file. Use "Path to firefox" -p -no-remote If you want to start a specific profile
See Also: → 1465447

bug 1541472 will make this obsolete in the interest of code and maintenance reduction when WebRender is enabled by default for everyone.

See Also: → 1541472
Flags: needinfo?(bas)

I'm marking this bug as INVALID per comment #2.

Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox69: affected → wontfix
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.