From cde88df9445364f3dd78427e55328fb7c4c7769e Mon Sep 17 00:00:00 2001 From: LloydNicholson <34131158+LloydNicholson@users.noreply.github.com> Date: Sat, 10 Oct 2026 12:17:06 +0200 Subject: [PATCH] Issue #126: web hosting guide no longer lists the unsupported ?cpu flag (#177) The web build always starts eframe's wgpu runner; only `?webgl` changes the backend. `?cpu` selected the same renderer as no flag, so drop it from the renderer table (and the HOSTING.md shipped in the web archive). Fixes #126. Co-authored-by: lloyd Co-authored-by: Claude Opus 5.5 --- packaging/web/README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/packaging/web/README.md b/packaging/web/README.md index dd885dc5a..7868b9507 100644 --- a/packaging/web/README.md +++ b/packaging/web/README.md @@ -82,7 +82,6 @@ WordCraft renders with wgpu. It uses **WebGPU** when the browser has it and fall |---|---| | *(none)* | WebGPU if available, otherwise WebGL2 | | `?webgl` | Force the WebGL2 backend (useful when a WebGPU driver misbehaves) | -| `?cpu` | Force the CPU canvas path (slowest, most compatible) | For example: `