Diego Gonzalez

@zcorpan We've updated the name in the explainer and the change in the implementation should be landing any day now. Thanks for the feedback. https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/DocumentSubtitle/explainer.md

Hola @DanielHerr Extensions are currently not in the scope of the API. We're still in the process of getting feedback but I'd encourage you to open a conversation in relevant...

hola @photopea! Thanks for the feedback. We definitely want a declarative entry point for the Install API. It is not discarded, and I think it's a perfect complement to the...

@photopea following up on this, do you have any use cases you require with the install API that the shape of the API wouldn't be able to fulfill? Please let...

Minimizing the number of errors implies we need to group them into categories that make it harder for a possible bad actor to accurately identify why an app installation didn't...

Explainer update to reflect this, view #961

The `.install` method could do a reasonable wait for the manifest link to be added or know that a manifest is being downloaded. In that case the promise would be...

@marcoscaceres are there any meeting notes from this meeting you had with @dmurph ? It is hard to followup on this conversation without context, special on a feature that my...

Thanks, appreciate the additional context. The promise indeed provides a way to do error handling for when the manifest doesn't load/isn't found/doesn't have an id, and with this 0 param...

The proposal has evolved with feedback from TAG and other browser vendors, including more recently, the debate over 'computed id'. Unlike oBIP install API needs transient activation. I think there...