Jake Archibald <jakearchibald@google.com>, 2017-01-23 15:50 +0000: > Archived-At: <http://www.w3.org/mid/CAPy=JooDcZghJcx=nnqu+Zw8BKhUFLydkk+-0rJ6cFJ9HXPZFA@mail.gmail.com> ... > Both MC and PG rely on up to two tabs plus a service worker being in memory > to make a payment work. This may cause problems with lower-memory devices - > I'm not sure. Requiring multiple tabs will definitely make the mechanism unusable by users on some (most) embedded browsers for TVs I’m aware of—certainly all the ones that are widely deployed in Japan on TVs (which despite that limitation are otherwise based on relatively modern browser engines). But then I’m not sure service worker could be made to work as expected in those browsers either. A payment-app interaction mechanism that doesn’t work on TV browsers seems less than ideal, but I also can’t imagine any way to make a workable user experience around it without multiple tabs. And given the way the platform is moving I reckon this is not characteristic unique to the payments case— there are other interactions that are not going to work on TV browsers or browsers on other devices that don’t provide for multiple tabs. —Mike -- Michael[tm] Smith https://sideshowbarker.net/
Received on Monday, 23 January 2017 16:28:22 UTC