Stable web version

[adamziel]

Let's make the web version of WordPress Playground work for the majority of use-cases. This means that using WordPress core and the popular plugins and themes should not yield any fatal errors, blank pages, or otherwise unexpected behaviors.

This means addressing all of the following issues:

• Web: YouTube embeds broken #411
• Adding a product to Woocommerce creates a critical error #602
• Missing CSS and images because the Gutenberg iframe isn't controlled by the service worker #646
• Playground not loading on Android and Chrome #564
• Links with target="top" don't work #266
• Privacy Sandbox compatibility #586
• Fatal error when the page is loading #603

Nice to haves:

• Multisite mode #499 (nice enhancement but not really a blocker here)
• Networking: Implement gethostbyname #400 (only makes sense if we can somehow provide a network proxy)
• wp_safe_remote_get request to an HTTPS site fails #396 (relies on networking support)

At the same time, it does not require addressing the following:

• PHP: Support proc_open #594 – it's more relevant for the CLI
• PHP: Build with pthreads support #347 – ditto
• Static assets of bundled plugins not recognized by service worker to rewrite request #109 – only matters for custom Playground builds
• Support wp_mail() #276 – Playground is not going to send emails from the browser
• Support Xdebug #314 – not relevant for using Playground on the web
• Network access in the browser #85 – non-starter without a hosted network proxy
• Create block theme: Google Fonts don't work #534 – not an error, it just needs a network proxy

[adamziel]

@dmsnell @danielbachhuber @eliot-akira did I miss anything here?

[danielbachhuber]

@adamziel Nothing that I'm strongly opinionated about, I don't think.

[adamziel]

All the "must haves" are now resolved. I'll close this issue and let's address "nice to haves" separately. If any major issue comes up, let's reopen.