Skip to content

DisplayXR Browser v1.0.10

Latest
Latest

Choose a tag to compare

View all tags
@displayxr-publish-bot displayxr-publish-bot released this 28 Sep 19:35
· 2 commits to main since this release
v1.0.10
869ff42

Highlights

  • DisplayXR Browser on desktop Linux. The first release with a Linux build: displayxr-browser_1.0.10-1_amd64.deb for Ubuntu 24.04 and 26.04 (GNOME). Web pages get the same glasses-free inline 3D as on Windows, woven through the DisplayXR runtime's service. The package depends on displayxr-runtime (>= 2.21.11) and bundles its own Khronos OpenXR loader.
  • Native Wayland and X11 / XWayland. Inline 3D runs in native Wayland windows and in X11 or XWayland sessions. Dragging a 3D window keeps the weave aligned: the window's position is phase-snapped to the panel, and on Wayland the move is synchronised with the woven frame.
  • Auto-3D, first phase (all desktop platforms). On supported WebGL pages (three.js, PlayCanvas) the browser can offer to show the scene in 3D. The choice is per site and is controlled from a "3D view" icon in the address bar, Ctrl+Shift+3, Page Info, a Settings category and an app-menu item. Administrators can set it with three enterprise policies: DefaultAuto3dSetting, Auto3dAllowedForUrls and Auto3dBlockedForUrls.

Features

  • Desktop Linux: GPU-process weave through XR_DXR_weave spec 12 (the woven origin comes back per frame), dma-buf frame hand-off and the woven draw-back (browser-pvt#163, browser-pvt#180, browser-pvt#167)
  • Desktop Linux: inline 3D is offered only on a panel the runtime drives. The page display-mode API, tab-driven panel 2D/3D switching and undocking to the native viewers all work as on Windows (browser-pvt#167)
  • Desktop Linux .deb: its own app id, profile and icons; no Google apt repository or cron job; a copyright file and third-party notices (browser-pvt#167)
  • The browser checks whether a DisplayXR runtime is installed before it starts. With none present, Windows no longer waits up to 8 s for the GPU-process window, and the auto-3D UI stays hidden. Linux uses the OpenXR loader's active_runtime.json lookup for the same check (browser-pvt#190, browser-pvt#192, browser-pvt#167)
  • Auto-3D content settings (auto-3d and per-origin tuning), a renderer injector that runs at document start, and the desktop UI described above (browser-pvt#191, browser-pvt#198, browser-pvt#199, browser-pvt#200, browser-pvt#201)

Fixes

  • Auto-3D strings are registered in both .gritdeps manifests, which fixes the resource build (browser-pvt#204)
  • Compile fix for base::DictValue at Chromium 155 (browser-pvt#202)

Built on Chromium 155.0.8059.12 (unchanged since v1.0.9).

Auto-published from displayxr-browser-pvt @ 9b759444170d63986b08348da0359b9e1a69a5fc.

Security updates follow Chrome stable. Every Chrome stable point release is rebuilt and published automatically when the browser's own code is untouched upstream, and verified on a DisplayXR display first when it is not. Not affiliated with Google; Google account sign-in and sync are not available.

Android APK: release-signed (CN=DisplayXR Browser). If you have any preview up to and including 0.1.24 installed, UNINSTALL it before installing this one - those were debug-key signed and Android refuses an install that changes the signing key (browser#188).

Linux (.deb, x64): sudo apt install ./displayxr-browser_1.0.10-1_amd64.deb - needs displayxr-runtime (>= 2.21.11) from DisplayXR/displayxr-runtime releases. A newer .deb upgrades in place; there is no apt repository.

Assets 5
Loading