Skip to content

Implement live Range boundaries for Code OSS highlights #741

Description

@wieslawsoltes

Active implementation checkpoint — 20 September 2026

Exact upstream heads are WebScene 3cc78ac28101e23f07ded947b44869277da6632d and AppScene acf42662309ea601720ed07c440cf183d7c73fe3; unchanged Code OSS is 645f29cc3176500b4b5762ba887cf2a7f0ffdf2c. Local vscode-demo is 06b5fa4328bae547e40462cbd049b6322f8e8d8e, clean, 294 commits ahead, and intentionally unpushed with Actions disabled.

Focused merge stacks

One-agent mode is enforced. No subagent is active. Reusable runtime behavior continues to land in WebScene or AppScene; unchanged Code OSS remains pinned. The change-related #752 and #753 runs passed. Broad PR CI/NuGet plus consolidation, post-merge main and previous-main runs were canceled to release runners; no WebScene job is intentionally retained between focused PRs. Full package, performance, visual, physical-platform and VM qualification remains deferred under the fast implementation directive; focused parser/native correctness and allocation checks are complete locally.

Next: finish the remaining planned CSS and product features, then physical Linux pixels, synchronization/device-loss/resize/soak/performance, visual comparison, VM/computer-use, and unchanged Code OSS Release qualification. Rich clipboard MIME, MULTIPLE/SAVE_TARGETS, recorded desktop-service/cross-platform work, workspace/Explorer, file/save, terminal, Markdown preview, accessibility, lifecycle, package-size, and no-browser promotion gates remain tracked and incomplete.

Parent: #740
Epic: #235

Scope

Implement the live Range boundary subset required before Code OSS Custom Highlight paint can be retained:

  • constructible Range plus document.createRange() using the active document/nested context;
  • setStart, setEnd, setStartAfter, setEndBefore, and selectNodeContents;
  • startContainer, startOffset, endContainer, endOffset, collapsed, and commonAncestorContainer;
  • UTF-16 text offsets and child-index element/document offsets;
  • browser-compatible collapse when one endpoint crosses the other;
  • same-root enforcement, detached/cross-document rejection, document-generation invalidation, and weak-wrapper cleanup;
  • preserve createContextualFragment() on the real Range prototype.

Acceptance

  • Same-node, cross-text-node, marker-sibling, nested-element, collapsed, invalid-offset, detached, and navigation cases are covered by focused contracts.
  • Boundary mutation performs ancestor/sibling work only when ordering must be compared and requests no frame by itself.
  • Repeated Range allocation/collection and navigation return native binding counts and V8 handles to baseline.
  • No DOM or visual-tree nodes are created for ranges and no Code OSS source changes are required.

Custom Highlight registry, functional pseudo cascade, and paint remain subsequent stacked work in #740.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestsize/Mvscode-oss/plannedPlanned for the AppScene/WebScene VS Code OSS integration

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions