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 /dom/interfaces/base/nsIDOMWindowUtils.idl | |
| 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 'dom/interfaces/base/nsIDOMWindowUtils.idl')
| -rw-r--r-- | dom/interfaces/base/nsIDOMWindowUtils.idl | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/dom/interfaces/base/nsIDOMWindowUtils.idl b/dom/interfaces/base/nsIDOMWindowUtils.idl index 8293c6c86..548214adc 100644 --- a/dom/interfaces/base/nsIDOMWindowUtils.idl +++ b/dom/interfaces/base/nsIDOMWindowUtils.idl @@ -50,7 +50,7 @@ interface nsIJSRAIIHelper; interface nsIContentPermissionRequest; interface nsIObserver; -[scriptable, uuid(7fcc7958-77d9-45ff-8c81-277bde5f0dc8)] +[scriptable, uuid(e23b3d3a-aa0c-4433-acab-07d4d25c1cc7)] interface nsIDOMWindowUtils : nsISupports { /** @@ -1414,12 +1414,11 @@ interface nsIDOMWindowUtils : nsISupports { readonly attribute boolean layerManagerRemote; /** - * Returns a Promise that will be resolved with a string once the capabilities - * of the h264 decoder have been determined. - * Success does not mean that all h264 video decoding will be done + * True if we can initialize a hardware-backed h264 decoder for a simple + * test video, does not mean that all h264 video decoding will be done * in hardware. */ - readonly attribute jsval supportsHardwareH264Decoding; + readonly attribute AString supportsHardwareH264Decoding; /** * Returns the current audio backend as a free-form string. |