Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Site doesn't load on Windows webkit due to audio context error #14105

Closed
Nav-2d opened this issue May 11, 2022 · 3 comments
Closed

[BUG] Site doesn't load on Windows webkit due to audio context error #14105

Nav-2d opened this issue May 11, 2022 · 3 comments

Comments

@Nav-2d
Copy link
Contributor

Nav-2d commented May 11, 2022

Context:

  • Playwright Version:1.21.1
  • Operating System: Windows
  • Node.js version: 14
  • Browser: WebKit
  • Extra: [any specific details about your environment]

Code Snippet

Help us help you! Put down a short code snippet that illustrates your bug and
that we can run and debug locally. For example:

test('example test', async ({ page }) => {
  await page.goto("https://monarch-test.tinyeye.com"); 
  await.page.pause();
});

// config.js
{
  name: 'Desktop Safari',
  use: { browserName: 'webkit' },
},

Describe the bug
This issue is related to #12823 and #13113

The site still doesn't load on Windows (webkit). The error in the console is attached
image

Tentative solution for now that works:

await page.addInitScript(() => {
    class AudioContext {}
    (window as any).AudioContext = AudioContext;
})
@mxschmitt
Copy link
Member

mxschmitt commented Aug 21, 2022

We could enable WEBKIT_OPTION_DEFAULT_PORT_VALUE(ENABLE_WEB_AUDIO PUBLIC ON) on Windows, that should fix it.

Update: Seems like ENABLE_WEB_AUDIO is not supported on Windows.

@zepumph
Copy link

zepumph commented May 10, 2023

I also just ran into this. Unfortunately, my project's stub for WebAudio is prohibitively complex, needing most functions in AudioContext and GainNode. It would be nice to support this general browser feature, at least in a formal stub.

@pavelfeldman
Copy link
Member

Why was this issue closed?

Thank you for your contribution to our project. This issue has been closed due to its limited upvotes and recent activity, and insufficient feedback for us to effectively act upon. Our priority is to focus on bugs that reflect higher user engagement and have actionable feedback, to ensure our bug database stays manageable.

Should you feel this closure was in error, please create a new issue and reference this one. We're open to revisiting it given increased support or additional clarity. Your understanding and cooperation are greatly appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants