Skip to content

[beta.2.2] Prove Native and Lit Framework Mode end-to-end #1339

Description

@SisyphusZheng

Part of #1321; depends on #1320 and shared Document #1326. Standalone Element baseline proof is #1338; cumulative consumer qualification is #1333/#1340.

Paired application acceptance

  • Equivalent Native/Lit list/detail/form/validation/success/error applications use file-generated records and one application protocol.
  • Loader -> SSR -> native claim or Lit hydration -> navigation -> action -> data refresh, plus redirect/404/errors.
  • Native POST progressive fallback with JS disabled; application-owned enhancement preserves method/body/status/headers.
  • Abort/newer-wins, back/forward, page exit/re-entry/remount and cleanup work in admitted browsers.
  • Hono executes selected handlers without rematching; layouts/Document do not add data schedulers.
  • Separate SSR and SSG; private request data never enters static public artifacts.
  • Router owns shared outcomes/context semantics; Native compiler/artifact protocol is absent from Lit runtime.
  • Explicit rendering selection; no universal hydration/DSD/CEM inference.
  • Qualify Lit reference runtime and publish unsupported/unverified cells; keep Native Cloudflare/Node/Deno and Bun/Nitro scope.
  • Packed consumer installs/develops/builds/runs without workspace aliases or routine framework edits.
  • Retain UI focus/keyboard/reconnect and foreign CE host binding evidence where used; no UI expansion.

Derive minimal interfaces from working implementations; do not freeze a speculative FrameworkAdapter. Use fixtures or independent consumers, not examples/**.

Governing plan (2026-09-08)

Maintainer-approved: ADR-0152, docs/current/VERSION_PLAN.md and #1341. Execution: https://github.com/orgs/open-element/projects/3. Acceptance checkpoints replace the three-day schedule. No automatic beta.2.4. Native/Lit are formal Framework Mode targets, not already-shipped support. Existing release records/versions remain unchanged; no closure without final-SHA evidence. examples/** stays frozen.

Accepted upstream-contribution priority — 2026-09-08

Native/Lit paired flows use upstream-aligned WTR component conformance while real SSR/navigation/POST remains in Playwright E2E. Separate generic Lit/WTR defects into recipient-native small reproductions and proposed patches; keep OE application protocol defects local. No upstream merge/timing gate or two complete SaaS requirement.

Use docs/architecture/infrastructure-reduction.md and VERSION_PLAN as scope. Prepare useful generic fixes for contribution through normal authorization; no invented bugs, cosmetic PR quota, or upstream-response release dependency. No migration is completed by this update.

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

    No labels
    No labels

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions