TPAC debrief
webapps cochair thoughts: ramping up. marcos did lots of work. getting others ready to take lead for chairing
Microsoft Lead:
Web Install Umbrella bug, UX bug, Discussion doc
OT is available in 143, and will run through 148
Feel free to share out this link to partners: web install API - navigator.install | Demos
Started a sync for <install>, notes can be found here – Project Install - Google Docs
Next instance this Thursday, looking forward to touching base with Dan
Issues – Issues · WICG/install-element
Mike meeting high level overview
ship simplest version of API out the door to OT to get data, to continue iterating on complicated design question for manifest fetching, attributes, needed, etc
eager to get same-origin out the door
want them to go together
Dan: why?
Alex: Focusing on cross-origin derisks the hardest part
Getting to a place / flow we can fall back to in the hardest case is the most important part.
if we don't understand site from and to, what is the flow to make that possible with highest confidence.
Vince: we want to push towards that as well
Google Lead:
Approximate Location API
Improve Gaming on the Web Interop by increasing WPT passing rates on Gamepad, Pointerlock and Screen Orientation APIs
Presented at TPAC
active work from Chrome team
Alex: are we feeling good about how that is going?
are we integrating with reporting APIs?
not now
current plan is developer documentation to come in later 2026 Q1
current plan is devtools output
discussion: how to use this?
install URL is wrong?
manifest IDs not matching?
Maybe monitor UKM to notice opportunities for improved migrations
Can we get the data into CRUX?
are we doing outreach / dev posts about this
enterprise comms
will publish in enterprise dev docs as well
if enterprise configures an old install, show a banner.
Do users see cross domain notice?
developers can arrange to not do that
Same site only, change in origin only if on same site. (eTLD+1)
Microsoft notes some teams have needed to do migrations and struggled with this some. Want to reach these developers with this feature launch.
warnings in devtools? reporting?
no manifest id in manifest?
migration configuration is wrong (install_url doesn't load?)
how to detect devs considering a move if they aren't engaging with any of our apis here.
reporting api
install_url redirected
manifest id didn't match
chrome ux report
people might not even know about the out-of-scope banner
report an origin has a high degree of out-of-scope banner? or..... start_url redirects out of origin?
Brainstorming session for mis-configured PWA scenarios?
Schedule a time;
do some pre-work to research through issues we are aware of
Navigation + scope extensions
This feature combination was overlooked and was recently fixed (as a priority for chat). Enabling capturing to still work with scope extensions.
this overlap edge case is handled:
we prioritize apps that are non-extended if there is overlap. otherwise scope control rules
a.com and b.com, b extends to a, we always capture a.com link to a.com app if both installed
Developer docs https://developer.chrome.com/docs/capabilities/pwa-navigation-management
FYI Discussion of PWA and powerful web applications work on fugu-dev thread