docs: macOS inline-3D weave-backend port design#26
Open
dfattal wants to merge 1 commit into
Open
Conversation
The browser builds+links on macOS today with the inline-3D WebXR API surface compiled in; only the weave backend is BUILDFLAG(IS_WIN)-gated. This is the blueprint for porting it, consuming the runtime's macOS XR_DXR_weave service (displayxr-runtime #760: IOSurface in/out, synchronous, batched). Key decision: implement the SYNC GPU-process path only and leave the async mojo bridge + DXGIHandle typemap Windows-gated — the mac runtime weave is synchronous by contract, so the async path (and its hard mach-port/IOSurface mojom typemap) earns nothing on mac. Collapses the port to a 5-PR plan (scaffolding+loader → views → GPU sync weave → CALayer compose → batch), with PR3+PR4 the critical path. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The DisplayXR Browser builds + links on macOS today (arm64, M150) with the inline-3D WebXR API surface compiled in — only the weave backend is
BUILDFLAG(IS_WIN)-gated (D3D11 + DirectComposition). This adds the port blueprint.Key decision: implement the synchronous GPU-process path only and leave the async mojo bridge +
DXGIHandletypemap Windows-gated. The macOS runtime weave is synchronous by contract (displayxr-runtime #760: IOSurface in/out, no fence), so the async path — and its hard mach-port/IOSurface mojom typemap — earns nothing on mac. This collapses the port to a 5-PR plan:InitializeCore(mac)/IsSupportedLocateViewsForRectmac, timespec time-conv)xrWeaveSubmitDXR)CARendererLayerTreeoverlay, no fence)PR3+PR4 are the critical path; the runtime half (#760) is already merged. Includes the full
IS_WIN-gate enumeration (21 sites), the transport substitution table, BUILD.gn/loader changes, and 6 open questions to verify in the live tree.🤖 Generated with Claude Code