1627432 - Forcing hardware acceleration doesn't work in some cases

Status: RESOLVED WORKSFORME

(Core :: Graphics, defect, P3)

Description

[Virtual_ManPL [:Virtual] 🇵🇱 - (please needinfo? me - so I will see your comment/reply/question/etc.)]

STR:

1. Get affected by patch from bug #1625857
2. Open about:config/Advenced Preferences
   and change:

• "layers.acceleration.force-enabled" preference to "true" value doesn't work as expected,
  it doesn't force enables disabled hardware acceleration
  and usage of Direct3D 11 (Advanced Layers) compositing, instead of Basic one
• "gfx.direct2d.force-enabled" preference to "true" value doesn't work as expected,
  it doesn't force enables disabled Direct2D
  (maybe it's because Direct2D requires Direct3D compositing)
• "layers.gpu-process.force-enabled" preference to "true" value works as expected,
  it force enables disabled GPU process
• "webgl.force-enabled" preference to "true" value works as expected,
  it force enables disabled WebGL2

Comment 1

[Virtual_ManPL [:Virtual] 🇵🇱 - (please needinfo? me - so I will see your comment/reply/question/etc.)]

Attachment: part of about;support.txt

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:bhood, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 4

[Bob Hood [:bhood]]

Is this issue still occurring with current releases of Firefox?

Comment 5

[Virtual_ManPL [:Virtual] 🇵🇱 - (please needinfo? me - so I will see your comment/reply/question/etc.)]

@ Bob Hood [:bhood] - I can not verify this issue, because I am not affected anymore by bug #1625857.

Comment 6

[Virtual_ManPL [:Virtual] 🇵🇱 - (please needinfo? me - so I will see your comment/reply/question/etc.)]

@ Bob Hood [:bhood] - The issue might still occur when someone will be affected by bug #1625857.