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 <lloyd@stackworx.io>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
authored and GitHub committed 2026-10-10 06:17:06 -04:00
1 parent 06be5d2ac8
commit cde88df944
1 file changed
-1
-1
View File
@@ -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: `<iframe src="https://example.com/wordcraft/?webgl" ...>`.