Web Browsers group meeting - April 16th, 2026

[kriswest]

Meeting Date

Thursday 16th April 2026 - 10am (US eastern timezone EDT) / 3pm (London, BST)

Zoom info

Register to the meeting series to receive an invitation:
https://zoom-lfx.platform.linuxfoundation.org/meeting/96615992377?password=88ed4841-afa2-41a6-8de3-e246967e5566&invite=true

Join Zoom Meeting:
https://zoom-lfx.platform.linuxfoundation.org/meeting/96615992377?password=88ed4841-afa2-41a6-8de3-e246967e5566

Meeting notices

• FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

• All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

• FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact legal@finos.org with any questions.

• FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

• A Discussion Group has no direct decision-making power regarding the FDC3 standard - rather it is intended that anything they propose or work on will result in proposals (via Github issues and PRs) for the Standards Working Group participants to consider and vote on for inclusion in the standard.

Participation Requirements

Note: Meeting participants are expected to accept the terms of the FDC3 license (Community Specification License), understand the governance process and have a CLA in place.

Please click the following links at the start of the meeting if you have not done so previously.

• View the CSL
• View the GOVERNANCE of the Project
• Click here to start a PR.
  • Edit the page to add your details.
  • Hit the save button.
  • Click "Create Pull Request".
  • Click "Accept" on the EasyCLA dialog in the PR's discussion section.
• Click here to send email to become a voting participant on the FDC3 Project

Agenda

• Convene & roll call, review meeting notices (5mins)
• Review action items from previous meeting (5mins)
  • Web Browsers group meeting - March 19th, 2026 #1803
• v2.2.2-beta.1 release testing
  • Additional changes for v2.2.2
    • Excess logging from fdc3-web-impl #1850
      • Reduce logs to debug level in fdc3-web-impl and remove excess logging in BroadcastHandler #1851
    • FDC3 Web reference implementation doesn't clean up properly on disconnect when using a MessagePort only #1853
      • Handle app disconnection in fdc3 reference implementation when working with a websocket #1854
    • V2.2.2-beta.1 regression: If the desktop agent changes the current user channel the agent-proxy is not aware of the change #1857
• Create a 'close' API call for apps to indicate they wish to be closed #1809
• Deprecate node 20 and change testing matrix to node 22, 24 & 25 #1826
• Allow apps to update their metadata that is returned in instanceMetadata #1846
• Automate maintenance of ContextTypes enum and type in fdc3-standard #1852
• AOB & Adjourn (5mins)

Minutes

• Previous Actions:

  • Ongoing:
    • Getting Started Guide work and homepage intro improvements to be continued by @kriswest and @robmoffat.
    • FDC3 API Metadata documentation still outstanding for @kriswest and @julianna-ciq. Issues for .NET/Golang updates to be raised after approval.
    • Marking the reference implementation as “not for production use” deferred to 3.0 scope (@kriswest).
    • Migration of example apps to the toolbox folder is in progress for @SeeWhatsOn and @robmoffat. Expanded demo migration issue (Rehouse FDC3 Example apps #1758) to include requirements and "good first issue" labelling.
  • Completed:
    • Removal of context-cleared event from 2.2.x branch (@kriswest).
    • Syncpack script fixed and Syncpack run on main (@kriswest, @Roaders).
    • AgentProxy now passes OriginatingAppMetadata, test coverage added (@kriswest or Open).
    • AppD documentation improvement PR AppD documentation improvements from AtharvaKathe18 #1799 approved and merged.
    • Minor reference implementation metadata PR merged.
    • Issue raised to automate generation of ContextTypes enum/type (Automate maintenance of ContextTypes enum and type in fdc3-standard #1852, @kriswest).
    • Console logging for visible control codes now confirmed resolved.

• v2.2.2-beta.1 Release Testing and Issues:

  • Release branch for v2.2.2-beta.1 created, with regressions fixed and merged.
  • Call for additional smoke testing of the release by users; feedback requested from @Roaders, @SeeWhatsOn, and @julianna-ciq.
  • Excess logging (fdc3-web-impl) resolved; logs reduced to debug and unnecessary logs removed.
  • Reference implementation now correctly cleans up on disconnect for both MessagePort and WebSocket scenarios.
  • Regression found: Desktop agent user channel changes are not always reflected in agent-proxy, causing missed broadcasts with external channel selectors. Action in progress by @kriswest for PR and release branch update.
  • Some pre-releases were inadvertently marked as "latest" on NPM; new workflow prevents recurrence and will be corrected in the next full release.
  • NPM Trusted Publishing transition required (Node 24, OIDC) before token expiry in 88 days.

• Create a 'close' API Call for Apps:

  • Consensus to add a 'close' API allowing apps (especially those running in iframes) to signal to the desktop agent to close themselves.
  • Method to return an error/reject if close is not possible.
  • No support for closing other apps or descendants in standard API.
  • @Roaders to add comment to the issue to ensure rejection is handled.

• Deprecate Node 20 & Update Testing Matrix:

  • Agreement to remove Node 20 from support and CI, and to switch test matrix to Node 22 and Node 24.
  • Discussion on benefit of matrix vs minimum version; consensus to set package "engines" to 22, and test primarily on Node 24.
  • Consideration for future testing against multiple TypeScript versions.

• No Mechanism for Identifying App Instances:

  • Discussion on adding instance identification for apps (e.g., conveying window title for instance disambiguation).
  • Options: Automatic proxy detection (e.g., via document.title) and/or explicit API to update title.
  • Agreement to return instance-specific metadata (including title) when an instance ID is provided, and update findInstances to return metadata objects.
  • Further comments to be added to Allow apps to update their metadata that is returned in instanceMetadata #1846 by @Roaders.
  • To be scheduled for v3.0 as a breaking change.

• Automate ContextTypes Enum Maintenance:

  • @kriswest to implement automation for ContextTypes enum and type generation in fdc3-standard.
  • Plan: Move definitions to fdc3-context, re-export via standard, and ensure future updates are schema-driven.

Action Items

• @kriswest and @robmoffat: Continue work on Getting Started Guide, incorporating previous feedback and homepage intro improvements.
• @kriswest and @julianna-ciq: Complete FDC3 API Metadata documentation and create .NET/Golang update issues after approval.
• @kriswest: Raise PR to mark FDC3 reference implementation as “not for production use”, set private, and stop NPM publishing (for 3.0 scope).
• @SeeWhatsOn or @robmoffat: Continue migration of example apps into the toolbox folder, set up separate build/test, and expand demo apps migration issue (Rehouse FDC3 Example apps #1758) with clear requirements.
• @kriswest: Test GetAgent console logging in Edge and Firefox to confirm no residual control code issues.
• @kriswest: Fix agent-proxy user channel regression, raise and merge PR, and create a v2.2.2-beta.2 if necessary for testing.
• @Roaders, @SeeWhatsOn, @julianna-ciq: Smoke test v2.2.2-beta.1 (and beta.2, if applicable) and report any issues.
• @kriswest: Update CI and package engines to deprecate Node 20, add Node 22/24, and review feasibility of TypeScript matrix testing.
• @Roaders: Add comments to 'close' API issue to ensure rejection cases are covered.
• @kriswest: Implement automation for ContextTypes enum/type from schema in fdc3-standard.
• @kriswest, @julianna-ciq: Schedule and attend working session to unblock API Metadata PR and resolve outstanding conflicts.
• @Roaders: Add comments to Allow apps to update their metadata that is returned in instanceMetadata #1846 on app instance identification and consider self-assigning for v3.0 implementation.

[Roaders]

Smoke tested the 2.2.2-beta.1 release and all looks good from here. I tested the main @finos/fdc3 package both with our own getAgent / DesktopAgentProxy implementations and with the finos implementations.

[kriswest]

Minutes posted
and v2.2.2-beta.2 was published to npm for testing last night, with the fix for DAs that set channels - a sample use case for that would be a reloaded layout where channels were set. @julianna-ciq any chance interop.io could test that case? We're also doing so here with the reference implementation.