FDC3 for Web Browsers & Bridging Discussion group - 17th July 2025

[kriswest]

Group overview

Discussion group focused on FDC3 use in Web browsers and the Bridging of FDC3 Desktop Agents to allow interop to span across them (based on similar techniques to FDC3 comms in a Web browser).

Software support for both FDC3 in a Web Browser and Desktop Agent Bridging are provided in the FDC3 2.2 NPM module: https://www.npmjs.com/package/@finos/fdc3/v/2.2.0

Relevant issue tags

Current open issues that relate to the above concepts with the labels:

Meeting Date

Thursday 17 July 2025 - 10am (US eastern timezone EDT/EST) / 3pm (London, GMT/BST)

Zoom info

• Join Zoom Meeting
• Meeting ID: 969 4029 4948
• Passcode: 636931
• Dial-in:

  Country	International Dial-in	Toll-free Dial-in
  US	+1 929 205 6099 (New York)	877 853 5247
  UK	+44 330 088 5830	0800 031 5717
  France	+33 1 8699 5831	0 800 940 415
  Find your local number	https://zoom.us/u/ad2WVnBzb8

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

Tracking Attendance

Note: Meeting participants are expected to add a comment to this GitHub issue in order that we can track attendance of FDC3 project meetings. Please do this at the start of the meeting.

Agenda

• Convene & roll call, review meeting notices (5mins)
• Review action items from previous meeting (5mins)
  • FDC3 for Web Browsers & Bridging Discussion group - 19th June 2025 #1618
• CJS build changes breaking Node consumers #1609 any volunteers to investigate?
• FDC3 Workbench intent raising control could be more intuitive #1612 any volunteers to remediate?
• Support the ability to specify where I would like a new app to open #1546
• Support for Multiple Application Scopes (Agents) within a single window process #1250 & Question: Disposal/Teardown patterns in FDC3 #1263
• Catch-up on any other work in progress:
  • Add property to support analytics across apps #1290
  • Missing source maps in npm packages #1589 (how has testing gone?)
  • Stop producing source maps #1629
• AOB & Adjourn

Minutes

• Convene & Roll Call, Review Meeting Notices

  • Meeting opened with a welcome to newcomer David Coxon (here.io).
  • Action items from the previous meeting were reviewed, including updates on context clearing, FQ AppIds, documentation, and open params.

• Review Action Items from Previous Meeting

  • FDC3 Workbench intent raising improvement highlighted as still outstanding.
  • Issues for fdc3.instrument and fdc3.instrumentList need to be written.
  • Proposal for extending Add property to support analytics across apps #1290 with getCurrentContext() written, pending discussion.
  • @kemereva's Context Clearing PR is awaiting review.
  • Fully Qualified AppIds work has been reviewed and merged.
  • Documentation clarification needed for repeated calls to addContextListener/addIntentListener.
  • @kriswest to raise the destructuring issue.
  • Source maps PR merged by @kriswest during the meeting.
  • Open params (Support the ability to specify where I would like a new app to open #1546) requires further discussion.

• CJS Build Changes Breaking Node Consumers (CJS build changes breaking Node consumers #1609)

  • Reported issues affecting FactSet.
  • No volunteers to address at present; @kriswest to follow up with FactSet.

• FDC3 Workbench Intent Raising Control Could Be More Intuitive (FDC3 Workbench intent raising control could be more intuitive #1612)

  • @Roaders plans to address this while working on another PR.
  • No other volunteers; request extended to any interested parties.

• Support the Ability to Specify Where I Would Like a New App to Open (Support the ability to specify where I would like a new app to open #1546)

  • Discussion covered three options for handling where new apps open:
    • Option 1: Provide space for custom metadata (supported by @julianna-ciq, @novavi).
    • Option 2: More complex approach (preferred by @Roaders, @paulgoldsmith).
    • Option 3: Do nothing (preferred by @SeeWhatsOn, @kriswest).
  • Mixed opinions; further participation on the issue encouraged.
  • Consideration of how to track usage if Option 1 is pursued.

• Support for Multiple Application Scopes (Agents) Within a Single Window Process (Support for Multiple Application Scopes (Agents) within a single window process #1250) & Disposal/Teardown Patterns in FDC3 (Question: Disposal/Teardown patterns in FDC3 #1263)

  • Limited discussion due to time constraints; topic to be main focus of next week's meeting.
  • @julianna-ciq shared an external use case for stitching React components.
  • @kriswest discussed potential resolutions for the open issue.
  • @novavi expressed hope for a timely solution.
  • Action to share presentation recording as a primer for the topic.

• Catch-up on Any Other Work in Progress

  • Add property to support analytics across apps (Add property to support analytics across apps #1290): Proposal for handling getCurrentContext() written and awaiting further discussion.
  • Source maps in npm packages (Missing source maps in npm packages #1589, Stop producing source maps #1629): Source maps PR merged by @kriswest; further testing and feedback pending.

• AOB & Adjourn

  • No additional business raised.
  • Meeting adjourned.

---

Agenda Items Not Discussed

• In-depth discussion on "Support for Multiple Application Scopes (Agents) Within a Single Window Process" (Support for Multiple Application Scopes (Agents) within a single window process #1250) and "Disposal/Teardown patterns in FDC3" (Question: Disposal/Teardown patterns in FDC3 #1263) was deferred due to time constraints. These topics will be prioritised in the next meeting.

---

Action Items

• @kriswest to follow up with FactSet regarding CJS build changes (CJS build changes breaking Node consumers #1609).
• @Roaders to address Workbench intent raising control improvements (FDC3 Workbench intent raising control could be more intuitive #1612).
• @kriswest and @julianna-ciq Discuss and progress Add property to support analytics across apps #1290, including the proposal for handling getCurrentContext() with metadata.
• @finos/fdc3-editors to review Context Clearing #1379, @kemereva to resolve test failure or another maintainer to merge it into a branch of the FINOS repo and do so.
• @kriswest to raise the destructuring issue.
  • DesktopAgentProxy implementation should support destructuring of all returned objects with functions and the Standard should recommend all implementations do #1638
• ALL: Further discussion and participation on open params (Support the ability to specify where I would like a new app to open #1546), especially comparing options.
• @novavi To share the presentation & recording on Multiple Application Scopes/Agents as a primer for next month's discussion.

Rolled over from previous meetings

• @julianna-ciq and @kriswest to create issues for the proposed solutions to Question: Strategy for Latest Context between two types: fdc3.instrument and fdc3.instrumentList while ignoring others #1616
• @finos/fdc3-editors & @kriswest complete review of Clarification re repeated addContextListener and addIntentListener calls #1394 and merge
  • @kriswest raise an issue for followup work on Clarification re repeated addContextListener and addIntentListener calls #1394

Untracked attendees

Full name	Affiliation	GitHub username

[paulgoldsmith]

Paul Goldsmith / Morgan Stanley 🕺

[novavi]

Derek Novavi / S&P Global

[david-coxon]

David Coxon / here.io

[kriswest]

Kris West / NatWest 🚀

[pvoznyuk]

Pavlo Vozniuk / RBC CM

[Roaders]

Giles Roadnight / Morgan Stanley 🚀

[SeeWhatsOn]

Chris Watson / Elgin White👋