226560 2021-06-02 16:50:23 -0700 Ensure run-safari keeps working 2022-11-14 03:31:21 -0800 1 1 1 Unclassified WebKit WebKit Misc. WebKit Local Build Unspecified Unspecified RESOLVED DUPLICATE 189234 https://bugs.webkit.org/show_bug.cgi?id=194808 https://bugs.webkit.org/show_bug.cgi?id=216783 https://bugs.webkit.org/show_bug.cgi?id=236968 https://bugs.webkit.org/show_bug.cgi?id=236829 https://bugs.webkit.org/show_bug.cgi?id=247823 InRadar P2 Normal --- 1 gsnedders webkit-unassigned achristensen ap marcos webkit-bug-importer oldest_to_newest 1766220 0 gsnedders 2021-06-02 16:50:23 -0700 We have historically broken run-safari on a variety of occasions. We should either: 1. Push everyone towards run-minibrowser and drop run-safari, to avoid giving people the expectation it works. 2. Set up some form of testing automation to ensure run-safari remains functional. 1766222 1 webkit-bug-importer 2021-06-02 16:51:26 -0700 <rdar://problem/78789239> 1766250 2 achristensen 2021-06-02 18:28:05 -0700 Last I heard our preferred solution for the overwhelming majority of these issues is rdar://74245355 1766657 3 marcos 2021-06-03 21:12:30 -0700 Breakages aside, the problem I ran into with Payment Request API is that minibrowser doesn't have - and probably never will have - ApplePay integration, which Safari does. So it was not possible for me to adequately test my patches. Having said that, Payment Request may be kinda unique in the way it interfaces with a system component. I'm not sure how many other APIs that do that, but it's something to consider if you go with option 1. 1912260 4 gsnedders 2022-11-14 03:31:21 -0800 *** This bug has been marked as a duplicate of bug 189234 ***