wangdequan/workinf_Blender_Wasm
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
Files
380cbed4ffc69f00e98a48c64deec84bbf8fa397
workinf_Blender_Wasm/docs/status/M14-04A.md
mes123456 380cbed4ff
Some checks are pending
M6 deployable RC / quick (push) Waiting to run
Details
M6 deployable RC / chromium (push) Blocked by required conditions
Details
M6 deployable RC / release (push) Blocked by required conditions
Details
Checkpoint web parity through Chromium input tasks
2026-08-19 10:39:03 -04:00

1.0 KiB
Raw Blame History

M14-04A Status

status: done
task: Chromium GPU/memory budget device tier selection
updated: 2026-08-19 America/New_York
enablingTask: false
parityStateChange: false

Scope

Added a bounded device-budget selector driven only by the real Chromium M14-01D identity report. The observed SwiftShader renderer and unavailable WebGPU adapter select CONSERVATIVE; untrusted, missing, or fallback adapters cannot expand budgets. Fixed CONSERVATIVE, BALANCED, and HIGH limits are explicit and unknown tiers fail closed. Firefox/WebKit are excluded by the iron rule.

Evidence

  • npm --prefix web run test:chromium-device-budget passed: 3 unit tests plus the production identity report checker.
  • Checker output: chromium-device-budget-ok tier=CONSERVATIVE reason=UNTRUSTED_ADAPTER identity=3c6f898e1b6ffd39862505b8e7dde8fd29369204e1670a013859f74ccaf1c1eb execution=DISABLED next=M14-04B.
  • npm --prefix web run typecheck and git diff --check passed.

Next Task

M14-04B: Chromium DPR 1/1.5/2/3 canvas and raycast consistency.

Reference in New Issue View Git Blame Copy Permalink