Skip to content

feat(browser): expose complete embedded document state #39

Closed

Description

@trmosala

What to build

An authorised-tab read includes nested and cross-origin document content, shadow content and usable frame identity, with explicit omission reasons.

Acceptance criteria

  • Ordinary, nested, cross-origin, sandboxed, srcdoc and transformed/clipped embedded documents are discoverable without extra approvals; geometry alone does not silently remove readable content.
  • Each document and interactive reference is bound to native tab, document and frame identity rather than URL or ordinal.
  • Open shadow content is included; otherwise inaccessible or nonsemantic rendered content is identified explicitly and exposed through available visual observation rather than silently claimed absent.
  • Bounded output reports excluded, unsupported, failed and truncated content distinctly; an empty frame list never hides known exclusions.
  • Frame replacement, navigation, revocation and cross-tab references fail safely with no fallback to a different document.
  • Fixtures use production-default routing and cover nested OOPIFs, source replacement and an embedded calendar shell.
  • In the existing authenticated Teams development instance, enabling only the Teams tab exposes the visible embedded Outlook calendar week and events; record tested runtime and minimal nonprivate parity evidence.

Blocked by

Context

Source: revised CM_Browser review and whole-tab Agent Access requirement, 2 October 2026. This is follow-up work to the previously completed bounded browser implementation; existing issues remain closed.

Preserve main-process ownership, explicit revocation, stale-target protection and isolation from unrelated tabs. Coordinate with ongoing browser changes and the separate Microsoft sign-in fix. Native validation must distinguish fixture results from actual authenticated-site evidence. Do not restart the installed app or server, modify real calendar events, or enter/change/submit timesheets.

Activity

  1. added
    enhancementNew feature or request
    ready-for-agentScoped work with acceptance criteria and recorded blockers
    on Oct 2, 2026
  2. trmosala commented on Oct 2, 2026

    @trmosala
    OwnerAuthor

    Implementation checkpoint saved; remaining acceptance work stays open.

    Embedded-document implementation and synthetic/native qualification are committed. Actual authenticated Teams/Outlook calendar parity acceptance remains unverified.

    Local commit: 7f746e8fcb7d2ad819b107aac2c0d7d9462d1361 on branch browser-gaps. This commit has not been pushed, merged or released.

    Fresh checkpoint validation: 410 tests / 6,620 assertions pass; all five affected package typechecks and the browser plugin build pass; native navigation and leave-confirmation reruns pass; scoped lint has 0 errors and 356 style warnings; formatting and whitespace checks pass. Earlier native fixture results are documented in the committed cm-browser README. These checks do not qualify authenticated Teams, macOS or a packaged app.

    Native UI screenshot and validation archive. No installed app/server was restarted and no real account data was modified.

  3. trmosala commented on Oct 3, 2026

    @trmosala
    OwnerAuthor

    Completed acceptance and pushed to browser-gaps at 2d582ec4484fad03b3f6792c1eab2275e682d1cf.

    The actual bundled browser plugin and sidecar exposed the authenticated Teams embedded Outlook calendar after one user-granted Teams-tab access decision. Hidden entries were expanded, all seven tested day views were read and a replaced calendar frame was safely reacquired through a fresh tab observation. The evidence retains loaded-item counts and runtime versions only, without private event content or account identifiers.

    Acceptance audit and nonprivate live parity evidence covers native nested/OOPIF discovery, identity binding, explicit omissions, bounded outputs and replacement/revocation isolation. Existing serial native qualification covers embedded-document and visual fixtures; fresh identity/inventory audit tests passed 2 tests / 11 assertions. The final related browser checkpoint passed 170 focused tests / 1,647 assertions, three native input/snapshot fixtures and desktop typecheck. The push hook passed all 31 configured typecheck tasks.

    Runtime: Windows x64, Electron 44.3.0, Chromium 152.0.7977.78. Exact launch artifact hashes were not pinned, so this is functional acceptance evidence with that provenance limitation, not a claim that the running app loaded the latest pushed artifacts. Source continuity is documented in the audit. Filtered calendar views do not establish backend completeness or worked time.

    Remaining authenticated input/scroll/event-detail acceptance is tracked in #40. This closure does not qualify macOS or packaged builds and does not represent a merge or release.

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 requestready-for-agentScoped work with acceptance criteria and recorded blockers

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions