Closed Bug 1694929 Opened 5 years ago Closed 4 years ago

audioworklet undefined in blank tab

Categories

(Core :: Web Audio, defect)

Product:
Core
Component:
Web Audio
Version:
78 Branch
Type:
defect

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: daniel, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux ppc64le; rv:78.0) Gecko/20100101 Firefox/78.0

Steps to reproduce:

Using 78.7.0esr-1 on Debian 10, tested on both x86_64 and ppc64le

  1. configure Firefox so that new windows/tabs are blank (no default page)
  2. open a tab
  3. press F12 for the dev console
  4. the the command:
    typeof AudioWorklet
    and press enter
  5. the result is "undefined"
  6. type a URL to view a web site
  7. repeat steps 3 and 4, now the result is "function"

Actual results:

at step 5, it says "undefined"

Expected results:

at step 5, should it always be "function"?

The Bugbug bot thinks this bug should belong to the 'Core::Web Audio' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Web Audio
Product: Firefox → Core

Should about:blank opened in a new tab be considered a secure context?

Severity: -- → S4

This is expected behaviour: in about:blank, if one opens the console and types window.isSecureContext, false` is returned, so the this is not a Secure Context, and so prototypes that require a Secure Context are not available.

I cross-checked with Chrome, and it does something weird, where AudioContext.audioWorklet is not present, so it's impossible to register an AudioWorkletProcessor, but the AudioWorkletNode prototype is available. Naturally, this isn't particularly useful, and is wrong per spec (AudioWorkletnode is Exposed=SecureContext)

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