diff options
| author | Matt A. Tobin <email@mattatobin.com> | 2022-05-17 00:13:54 -0500 |
|---|---|---|
| committer | Matt A. Tobin <email@mattatobin.com> | 2022-05-17 00:14:28 -0500 |
| commit | d5b9a341b8fc83017590d4a435bee27c5a106c66 (patch) | |
| tree | 25151a190a3a9407c2e4ac00701b8ffb8961b086 /mach | |
| parent | d4ee07aad33c1e6817f558c46e849a7f0143bda2 (diff) | |
| download | aura-central-d5b9a341b8fc83017590d4a435bee27c5a106c66.tar.gz | |
[DOM:Media] Revert Bug 1212323 Parts 2 and 3 where supportsHardwareH264Decoding() uses a promise if MP4 Hardware Acceleration to about:support
This concern was largely Mac-specific but I did leave Part 1 intact because the Mozilla Bug makes a good point that some systems may always software render a 64x64 video (specifically apple but other implementations could adopt this nonsense as well). Personally I want accelerated video.. damn it!
The real question is.. Why was the promise never resolving in the first place? Is it fall out from killing DOM Promise? It used jsval but who the hell knows or even cares.. It works and can once again be queried without jumping through god damned hoops.
Diffstat (limited to 'mach')
0 files changed, 0 insertions, 0 deletions