To be more specific (I thought I had filed a bug about this but apparently it was lost in tabs half-written...): the single call to boardcastChannel.postMessage(...) is what kills Safari and Edge. I don't personally see the benefit of allowing those two to just die off for a single function call (wrapping it in a try allows them to work again) but the newer the feature we require the smaller the range of browsers we'll allow to work.
If the consensus is that Chrome is the new official client we should probably state that outright (gross). If not, we need to weigh the importance of any feature so new that it's only supported by 1-2 browsers. (And like Dan says, Chrome on iOS doesn't work either because it's the iOS webkit engine under the Chrome UI and syncing services.) I guess I should get that bug written up finally. Jason -- Jason Boyer Indiana State Library 315 W. Ohio St. Indianapolis, IN 46202 http://library.in.gov/ ________________________________ From: Open-ils-general <open-ils-general-boun...@list.georgialibraries.org> on behalf of Dan Scott <d...@coffeecode.net> Sent: Monday, January 29, 2018 10:37 AM To: Evergreen Discussion Group Subject: Re: [OPEN-ILS-GENERAL] Web Client on IOS **** This is an EXTERNAL email. Exercise caution. DO NOT open attachments or click links from unknown senders or unexpected email. **** ________________________________ I'll add this to the bug, but the underlying reason is that on iOS all browsers are forced to use the Safari browser's engine; this means that any of the standards-based enhancements that Firefox and Chrome bring to other platforms, such as Service Workers (used in the Web Staff Client for offline transaction support etc), won't work on iOS until Apple updates Safari to support those standards as well. In short: to make the web staff client work on iOS in even a limited fashion, the Evergreen developers will have to add Safari to the supported web browser list. Requiring developers to have an iOS device to even start debugging this particular issue is a barrier for some of us. On Mon, Jan 29, 2018 at 10:19 AM, Tim Spindler <tjspind...@gmail.com<mailto:tjspind...@gmail.com>> wrote: FYI, I just opened a bug on this. https://bugs.launchpad.net/evergreen/+bug/1746020 On Mon, Jan 29, 2018 at 10:08 AM, Jason Stephenson <ja...@sigio.com<mailto:ja...@sigio.com>> wrote: On 01/29/2018 09:18 AM, scott.tho...@sparkpa.org<mailto:scott.tho...@sparkpa.org> wrote: > Hi, > > Has anyone had any luck getting the Web Client to work on an iOS > device? I tried both the Firefox and Chrome apps. The menus appear, but > no login is generated. Any insights would be appreciated. The short answer is no. It's not working on an iPhone here. When you go to the login page, it is pretty much blank. No box to enter credentials. This is happening with Evergreen 3.0.3. I recommend opening a bug on Launchpad. Jason > > Thank you, > Scott > > > > Scott Thomas > > Executive Director > > *PaILS / SPARK* > > (717) 873-9461<tel:%28717%29%20873-9461> > > scott.tho...@sparkpa.org<mailto:scott.tho...@sparkpa.org> > <mailto:scott.tho...@sparkpa.org<mailto:scott.tho...@sparkpa.org>> > > Stay informed! Join the SPARK-User Email List: > > https://mail.palibrary.org/mailman/listinfo/spark-users > > Description: Description: Training | SPARK – Pennsylvania's Statewide > Library System <http://www.palibrary.org/pails/> > > > -- Tim Spindler tjspind...@gmail.com<mailto:tjspind...@gmail.com> P Go Green - Save a tree! Please don't print this e-mail unless it's really necessary.