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

As another example, WebKit on iOS has a completely different compositing model than WebKit on macOS (compositing is done using different API in browser’s process in iOS but done in Web content’s process in macOS). As a result, any features that affect stacking context, hit testing, or scrolling would need be implemented separately twice. Should we consider two of these WebKit ports to have multiple independent implementations of all relevant features? I don’t think so.

-- 
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-578275866