Description: Investigate FMS behavior across browsers and platforms. Targets: Safari (WAAPI quirks), Firefox (prefers-reduced-motion differences), Chrome (compositor offloading edge cases), mobile WebViews especially in Teams clients. Cross-reference against any existing bug reports. Audit by running a representative set of motions across all targets, capturing observed inconsistencies. Land small workarounds in scope (e.g., a feature-detection guard, a workaround for a specific Safari quirk). Defer larger compatibility refactors.
Why it matters: FMS ships to consumers across the entire M365 surface, including Teams desktop's older WebView contexts. Cross-browser correctness is a Stable promotion implicit gate, even though the v9 checklist doesn't enumerate it explicitly.
- Difficulty: Medium (testing burden is real; analysis is moderate)
- Sequencing: M3 W9–10
- Tags:
partner-pickup
- Note: This audit benefits from access to Teams desktop's specific WebView versions; coordinate with shift or a Teams engineer if needed
Description: Investigate FMS behavior across browsers and platforms. Targets: Safari (WAAPI quirks), Firefox (
prefers-reduced-motiondifferences), Chrome (compositor offloading edge cases), mobile WebViews especially in Teams clients. Cross-reference against any existing bug reports. Audit by running a representative set of motions across all targets, capturing observed inconsistencies. Land small workarounds in scope (e.g., a feature-detection guard, a workaround for a specific Safari quirk). Defer larger compatibility refactors.Why it matters: FMS ships to consumers across the entire M365 surface, including Teams desktop's older WebView contexts. Cross-browser correctness is a Stable promotion implicit gate, even though the v9 checklist doesn't enumerate it explicitly.
partner-pickup