FDC3 for Web Browsers & Bridging Discussion group - 19th Feb 2026 #1763
Description
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 19th Feb 2026 - 10am (US eastern timezone EDT/EST) / 3pm (London, GMT/BST)
Zoom info
Join Zoom Meeting:
https://zoom-lfx.platform.linuxfoundation.org/meeting/96615992377?password=88ed4841-afa2-41a6-8de3-e246967e5566
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
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)
- Progress on FDC3 2.2.2 and/or 2.3.0 release prep
- [DONE] fix the progress reporting in conformance tests #1748, Stop fdc3-web-impl delivering broadcast messages back to the sender #1749, Bump ajv from 8.17.1 to 8.18.0 #1759
- Removed version numbers from conformance test names #1726
- test: convert AppDirectory test to Jest and run in CI #1720 & Bump ajv from 8.17.1 to 8.18.0 in /packages/fdc3-standard/src/app-directory/specification/test #1761
- Esm modules fix #1677
- Migrate to MUI 5 #1714
- feat(context): add instrument classification property #1665
- Conformance tests should confirm matching FDC3 version number is returned #1750 & Conformance tests should accept both unqualified and fully qualified app ids as valid responses #1762
- Question: Where to rehouse FDC3 Example apps #1758
- Improve Error Reporting When Desktop Agent *adaptor* Iframe doesn't load #1733
- AOB & Adjourn (5mins)
Meeting Minutes
-
Review of Previous Action Items
- Many previous actions remain open; see action items below for carried-over or updated items.
- Discussion on "select agent functionality" issue ("Select Agent" Functionality #1685) concluded it should be removed from meeting actions until a proposal for handling it added to the issue and the existing comments dealt with. The GitHub issue remains open, but should be closed if it is not updated further.
- Getting Started Guide/course material: @robmoffat sent material to @kriswest; action to engage external feedback (Andrew Aitken and Andrew McDonald) and consider homepage/intro improvements.
- Managed browser extension proposal: @kziemski is progressing, considering where to host experimental projects (personal repo or FINOS Labs). Community feedback to be sought via issue/discussion.
- FDC3 API Metadata documentation and related reference implementation actions are delayed (by focus on the next release which will not include them), to be rolled over.
- Reference implementation actions marked as low priority pending release focus.
- @Roaders continues work on ESM modules fix; .NET agent conformance test still pending.
- Other feedback/review PRs for FDC3 API Metadata and 2.2.2 release PRs completed.
-
Progress on FDC3 2.2.2 and/or 2.3.0 Release Prep
- Maintainers agreed to prepare both 2.2.2 (bugfixes, conformance changes) and 2.3.0 (if new features/tests are complete).
- Decision to surgically remove context-cleared event and associated code from 2.2.x to maintain SEMVER (feature will be in 2.3.0 or 2.0.0 after tests/coverage improved).
- Fixes merged: progress reporting in conformance tests, stop broadcast to sender, AJV bumps,
- AppDirectory test converted to Jest/CI, ESM modules fix, migration to MUI 5, instrument classification property (pending).
- Schemas found to be partly invalid (use of unevaluatedProperties/draft 07 of JSON schema mismatch); further PRs to correct are needed.
- AppDirectory schema/test fix: consensus to push quick correction to align with intended meaning; to be checked with Standards WG.
- ESM modules fix: major changes led by @Roaders, tested and pending final review (esp. CommonJS build validation – @hughtroeger to confirm).
- MUI 5 migration: will proceed after ESM fix to avoid conflicts.
- Instrument classification property change approved, to be released with 2.3.0 or 3.0.0 only.
-
Conformance Tests – Version Reporting & App ID Matching
- Agreement to improve conformance tests:
- Ensure returned FDC3 version number is at least the tested version (not just exact match).
- Accept both unqualified and fully qualified app ids as valid responses.
- @Roaders to raise small PRs as fixes are developed during .NET agent conformance work; will not block 2.2.2 release but will be backported if needed.
- Agreement to improve conformance tests:
-
Where to Rehouse FDC3 Example Apps
- Discussion on whether demo/example apps should reside in the main repo or separate "toolbox" or FINOS Labs repo.
- Consensus: move/maintain in toolbox folder, with clear build/test separation.
- @SeeWhatsOn to create/expand a GitHub issue with detailed requirements and mark as "good first issue" for external contribution/university students.
-
Improve Error Reporting When Desktop Agent adaptor Iframe Doesn't Load
- Issue acknowledged (raised by @robmoffat): current errors unclear when iframe does not load.
- @kriswest to consider, but not a blocker for this release.
-
AOB
- Logging control characters issue in GetAgent console logs highlighted (Chrome flag change causing visible control codes); open to contributors to fix.
- Zoom link confusion noted; @kriswest to clarify/update meeting templates and respond to affected participant.
Action Items
- @kriswest and @robmoffat: Continue work on Getting Started Guide, incorporating external feedback and homepage intro improvements.
- @kziemski: Continue progress on managed browser extension proposal; raise GitHub issue/discussion for community input.
- @kriswest: Complete FDC3 API Metadata documentation changes and create related issues for .NET/Golang updates after approval.
- @kriswest: Raise PR to mark FDC3 reference implementation as “not for production use”, set private, and stop NPM publishing.
- @Roaders: Run and report conformance tests against .NET agent.
- @kriswest: Remove context-cleared event and related changes from 2.2.x release branch; validate and prepare for 2.2.2 release.
- @kriswest/@robmoffat/@Roaders: Review/finalise ESM modules fix, including CommonJS build validation (@hughtroeger).
- @SeeWhatsOn: update Migrate example apps into toolbox folder with separate build/test as per discussion; support /others with "good first issue."
- @SeeWhatsOn: Expand the demo apps migration issue (Question: Where to rehouse FDC3 Example apps #1758) with clear requirements (based on migration into a /toolbox/fdc3-examples folder) and mark as "good first issue."
- Open to all: Review GetAgent console logging for visible control codes; propose a fix.
- @kriswest: Connect with @julianna-ciq on metadata/JSDoc progress for 3.0 planning.
- @Roaders: Progress fixes for conformance tests to accept both qualified/unqualified app IDs and improved version checking; submit PRs as issues are found during .NET agent testing.