Fwd: Notes - Fugu Community Monthly sync EMEA friendly (Jan 26, 2026)
Vincent Scheib
Web Install
Preparing for Origin Trial, Targeting M146
Discussing what should happen if the <install></install> element is in an already installed standalone window. Dan has proposed it should open the app in standalone.
Link to section of UX review doc – Google (Chrome) / Microsoft (Edge) Sync - Project Web Install - Google Docs
Google chat review thread – Re: <install> Element UX review
Tracking bug – [<install> element] Transform to "Open in Chrome" for <install></install> within a standalone window [475285741] - Chromium
Discussed that web developers would expect.
Ideally web developers would not display the element when already installed.
Make this configurable?
still need a default.
Brainstorm of what happens if the element is still there?
'open in'
new window
new browser tab
'install' (same as below)
'✅ installed' - on click..
Nothing, not clickable. but needs the element to not look interactable
(consensus that this is likely best solution)
show custom dialog explaining what being installed means, similar to the install flow already.
shows app info?
open new instance
hide element
Edge:
Haptics
Edge has some early ideas on web haptics. Looking to understand developer interest/early feedback before we decide on whether to invest - MSEdgeExplainers/Haptics/explainer.md at main · MicrosoftEdge/MSEdgeExplainers
old version: https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/HapticsDevice/explainer.md
mattre...@google.com has spent time on this
Samsung may be interested?
target groups WICG and or Device and Sensors
Developer demand?
if e.g. in design tools such as Figma, would be nice to have feedback when snap actions have completed.
Window Controls Overlay
Considerations on removing WCO toggle - Removing Window Control Overlay Toggle
Discussed:
Chrome team recently discussed this partially - considering having one platform not using the toggle. However the decision was to keep the toggle.
Agreed that landing code that enabled the 'no toggle' version to exist made sense. Edge may wish to ship this and Chrome may monitor and follow after some time.
2026 plans?
Chrome teams mostly have annual plans in place.
pwa
app migration
macOS notification attribution
safebrowsing, increased integration with context of PWA install
install dialog improvements
install entry point UX experiments
navigation capture tech dept clean up
device
approximate geolocation
considering AI model change for text detection api
gamepad API interop 2026
keyboardlock in fullscreen api
audio
configurable render quantum
playout statistics API
Edge planning at approximately 6-8 week time frame.