#264 Tracking: close remaining Messenger Desktop capability gaps

[Anonymous]

Originally created by: kristofferR

Goal

Turn the clean-room comparison of Messenger Desktop v1.9.0-3 into a deliberate Carrier roadmap.

This tracker covers useful behavior discovered through public release artifacts, runtime observation, and comparison with Carrier's existing implementation. It is not a request to copy third-party source or reproduce unsafe implementation choices.

Priority rules

• P0: current correctness, login compatibility, rendering, or platform reliability
• P1: important capability, recovery, distribution trust, or native integration
• P2: valuable polish or opt-in advanced behavior
• Items are listed in recommended implementation order within each tier.
• A later item may proceed in parallel when it has no dependency on an earlier item.

P0 — correctness and compatibility

1. [x] [#243] — make muted-conversation notification and badge detection correct (shipped in v1.12.0; closed after no further reporter feedback)
2. [x] [#254] — prevent compact Messenger popovers from being treated as full media viewers (merged in [#273])
3. [ ] [#251] — support tightly scoped native popup windows for social-login flows
4. [ ] [#250] — replace CSS page scaling with native WebView zoom
5. [x] [#255] — harden pure-Wayland startup and add a Niri/WebKit safe mode (merged in [#274])
6. [ ] [#253] — reconcile unread notifications across Messenger inbox filters

P1 — core capability and platform quality

1. [ ] [#186] — sign Windows releases with Authenticode
2. [ ] [#252] — support safe attachment downloads and a persistent Downloads view
3. [x] [#257] — improve camera and microphone permission recovery (merged in [#275]; live verification tracked in [#28])
4. [x] [#258] — adopt an engine-aware user-agent compatibility policy (merged in [#278]; authenticated and full cross-platform verification remain pending)
5. [ ] [#256] — add native fullscreen and resilient window recovery controls
6. [ ] [#259] — add dot badges, badge-only muted behavior, and notification test controls
7. [x] [#261] — restore standard macOS Services and Window menu integration (merged in [#277]; tested on macOS 27, oldest-supported macOS remains untested)

P2 — polish and advanced options

1. [ ] [#263] — expand context-menu coverage for media and attachment links
2. [ ] Add one-time notification setup and a live privacy preview (original issue [#260] was deleted; completion is not established)
3. [x] [#262] — choose how often to check for updates, and show release notes in the update prompt

Validation gate

• [ ] [#28] — complete Windows and Linux manual testing as the P0/P1 platform-validation gate
• Benchmark startup, idle CPU, resize/scroll smoothness, and memory before and after rendering-sensitive changes.
• Test every security-sensitive flow with a hostile remote page assumption.
• Verify update, download, popup, and permission behavior on all supported platforms.
• Record any rejected item here with the reason instead of silently dropping it.

Guardrails

• Keep the Messenger origin unable to invoke broad native commands.
• Do not globally relax Tauri capabilities, CSP, navigation, or popup policy.
• Never permit executable, script, or installer downloads through the attachment path.
• Do not reparent Messenger's React-owned DOM to implement fullscreen or media behavior.
• Do not open privacy settings, release pages, installers, or external URLs without a user action.
• Keep updates signed, explicit, reversible where safely possible, and disabled when a platform package manager owns installation.
• Preserve privacy: tests and previews must use synthetic content, and diagnostics must not retain message text or identifiers.

Completion criteria

• All P0 items are closed or rejected with a documented technical reason.
• P1 items have cross-platform verification appropriate to their scope.
• Rendering-sensitive changes have before/after measurements rather than assumed performance claims.
• The validation gate is complete before declaring functional parity.
• Remaining P2 work is either shipped or explicitly deferred with rationale.

[Anonymous]

Originally posted by: kristofferR

[!NOTE]
🤖 GPT-6 responding on behalf of Kristoffer

PR [#273] and PR [#274] are merged, completing the implementation work for [#254] and [#255]. Both issues now have completion comments and are closed; their P0 tracker entries are checked off.

The remaining live Messenger, compositor, and rendering-performance checks are retained in [#28]. The overall validation gate and the other roadmap items remain open.

[Anonymous]

Originally posted by: kristofferR

[!NOTE]
🤖 GPT-6 responding on behalf of Kristoffer

Marked [#257] complete following the merge of [#275] (ffb74e7): contextual camera/microphone recovery, native macOS permission status and explicit requests, scoped settings actions, and platform-appropriate guidance are implemented.

Remaining live permission-flow verification is explicitly tracked in [#28]. The overall capability-gap tracker and platform-validation gate remain open.

[Anonymous]

Originally posted by: kristofferR

[!NOTE]
🤖 GPT-6 responding on behalf of Kristoffer

Reviewed the remaining roadmap items against merged work and v2.0.0. No additional item has enough completion evidence to check off. GitHub confirms [#260] was deleted (HTTP 410), so its entry now records that explicitly and remains unchecked rather than implying the work shipped. The platform-validation gate in [#28] and the remaining capability items stay open.

[Anonymous]

Originally posted by: kristofferR

[!NOTE]
🤖 Claude Opus 5.5 responding on behalf of Kristoffer

Closing this tracker. [#250] (native zoom, [#324]) and [#251] (scoped popups, [#344]) are now done too. [#28] is closed. The remaining items each have their own open issue: [#253], [#186], [#252], [#256] and [#263]. The "one-time notification setup and live privacy preview" entry had no issue left (#260 was deleted), so it is dropped rather than tracked here.

[Anonymous]

Ticket changed by: kristofferR

• status: open --> closed