DisplayXR Browser preview-0.1.35

DisplayXR Browser — Developer Preview · built on Chromium 154.0.8037.17

A Chromium-based browser that renders the whole web normally and weaves glasses-free inline-3D for
inline-3d WebXR pages on DisplayXR hardware. Windows / D3D11 + DirectComposition. Requires a DisplayXR
3D display + the DisplayXR runtime and a display plug-in (the installer chains/detects them); on any
other machine it is an ordinary browser.

What's new

• Chromium 154.0.8037.17 (from 153.0.8010.27): the full 179-patch series re-anchored; from here the
  pin follows Chrome stable automatically (chromium-watch + auto-rebase).
• Native immersive-vr is now the default in-tab path (0142–0179, 0183): a stock immersive-vr
  WebXR app (three.js, Babylon, A-Frame) converts on a plain double-click of the browser icon — no launch
  flags — weaves in-tab (windowed or fullscreen), takes controller input and exits cleanly. The vendored
  content-script shim remains available as --immersive-vr-shim; --no-immersive-vr-emulation still
  means neither path. Android: compiles and is enabled, not yet exercised on an Android panel.
• inline-3D: a zero-identity tile rect is never suppressed unwoven and legacy rects tolerate the 1-px
  channel skew (0182, browser#113/#99); the tracked-rect carrier is named in the cc log for diagnosis
  (0181, browser#104). Includes everything from 0.1.34 (mono-in-place chain, GPU stage cap fix).
• No more "Google API keys are missing" infobar on launch (browser#117): the build now carries API key
  GN args (placeholders; Google-backed features stay off).

Verified on hardware against runtime v2.16.24: stock inline-3D samples page (woven, flat mono past the
window edge, no marks), xrdinosaurs immersive-vr (windowed + fullscreen, exit VR), first launch clean.

⚠️ Developer preview. Rebased onto Chrome stable automatically, but security point releases are
not yet promoted without a human — don't use it for sensitive browsing; use your primary browser for
banking, etc. See the maintenance policy.