Re: [w3c/manifest] Moves BeforeInstallPrompt and related text to a non-normative annex. (#843)

> @marcoscaceres's argument about "engines, not browsers" (to paraphrase) is deeply problematic in this instance. Nearly all of the work of providing UI for installation is browser specific. Samsung Internet, Chrome, UC, Opera, and others all have separate implementations of these surfaces.

Whether UI itself has multiple implementations or not is irrelevant since that’s not a normative part of the specification (if it were, that would be also deeply troubling). What’s normative & observable by web content is the Web API surface, and that does not have multiple independent implementations.

Also, if we were to accept your argument that “UI is implemented independently,” then a similar argument can be made for any Web API that has significant platform integration. Almost everything related to form control rendering, UI events such as pointer events, and user interactions like drag & drop on iOS and macOS are implemented independently in WebKit. Yet, I don’t think we should consider Safari on iOS and Safari on macOS to be two independent implementations of respective specifications because the underlying engine which expose those API is the same.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/pull/843#issuecomment-578272816