Comment 8 for bug 1899270

Here are the first sections of chrome://gpu output without and with --ignore-gpu-blacklist. The only difference is in Hardware Protected Video Decode which is 'Unavailable' in the first case and 'Hardware Accelerated' in the second.

Note, also, that both of these lists are different to the output that I posted a couple of days ago where, despite my having written that Hardware Acceleration was turned on in chrome://settings, I believe it was still actually turned off when I captured the output. (I've a feeling that although I changed the setting I didn't click the Relaunch button.) Please accept my apologies for this, I hope it hasn't caused much confusion. For confirmation, I've reattached the full set of chrome://gpu output captured without --ignore-gpu-blacklist.

B

> /opt/google/chrome/chrome

Graphics Feature Status
Canvas: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Out-of-process Rasterization: Disabled
OpenGL: Enabled
Hardware Protected Video Decode: Unavailable
Rasterization: Software only. Hardware acceleration disabled
Skia Renderer: Enabled
Video Decode: Software only. Hardware acceleration disabled
Vulkan: Disabled
WebGL: Hardware accelerated
WebGL2: Hardware accelerated

> /opt/google/chrome/chrome --ignore-gpu-blacklist

Graphics Feature Status
Canvas: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Out-of-process Rasterization: Disabled
OpenGL: Enabled
Hardware Protected Video Decode: Hardware accelerated
Rasterization: Software only. Hardware acceleration disabled
Skia Renderer: Enabled
Video Decode: Software only. Hardware acceleration disabled
Vulkan: Disabled
WebGL: Hardware accelerated
WebGL2: Hardware accelerated