Adopt an engine-aware user-agent compatibility policy
Facebook Messenger on your desktop, without the Facebook clutter
Brought to you by:
kristoffer-r
Originally created by: kristofferR
Carrier currently uses a fixed browser user agent. A static Safari or Chromium version eventually becomes stale and can claim capabilities that the actual WebView engine does not provide, especially when WebKitGTK is presented as Chrome on Linux.
That can create authentication, feature-detection, and compatibility problems over time.
Use the least invasive user-agent policy that keeps Messenger compatible while accurately representing the embedded engine.
Originally posted by: kristofferR
Implemented in PR [#278], merged as d97e467. Carrier now uses each WebView's native user agent, with a centralized compatibility policy and tests for platform selection and native fallback.
All required local checks passed. The Linux WebKitGTK probe reached the login form; authenticated functionality and the full cross-platform compatibility matrix remain unverified and are documented in docs/user-agent-policy.md.
Related
Tickets:
#278Ticket changed by: kristofferR