rszimm / sprinklers_pi

Sprinkling System Control Program for the Raspberry Pi
GNU General Public License v2.0
310 stars 100 forks source link

safari on iOS 9 no longer supports sync ajax requests #44

Closed codekitchen closed 5 years ago

codekitchen commented 8 years ago

sprinkers_pi doesn't work on iOS 9 Safari, because it specifies async: false for all the ajax calls, which Safari no longer supports.

Everything actually seems to work fine by just removing that option and allowing the ajax calls to run asynchronously, but I'm not positive yet that this doesn't introduce some race conditions, so I need to do more testing before opening a pull request.

Stifler6996 commented 8 years ago

I dont know about web coding, but I see some problems with the web pages using IOS9 also. If you have all 15 outputs configured for example. From the main page, goto manual. You cannot scroll down past what is visible. refresh the page, and everything is fine again.

Also, occasionally when hitting any 'back' button from a sub menu, will return you to a blank page. Hit refresh and it becomes good again.

rlabatt commented 8 years ago

I’ve had similar issues and have found that using FireFox can help. That said, Safari is a much better experience than Chrome, which is not happy about spi.

On Dec 4, 2015, at 14:02, Stifler6996 notifications@github.com wrote:

I dont know about web coding, but I see some problems with the web pages using IOS9 also. If you have all 15 outputs configured for example. From the main page, goto manual. You cannot scroll down past what is visible. refresh the page, and everything is fine again.

Also, occasionally when hitting any 'back' button from a sub menu, will return you to a blank page. Hit refresh and it becomes good again.

— Reply to this email directly or view it on GitHub https://github.com/rszimm/sprinklers_pi/issues/44#issuecomment-162094008.

Stifler6996 commented 8 years ago

I used Firefox and I experience this:

When Scrolling to the bottom, this occurs. The "SAVE" button pops up at the top. Is this also an Ajax thing?

codekitchen commented 8 years ago

No, that wouldn't be related to this issue. It may even be intentional, I'd have to dig into the code to be sure. But it should be tracked in a separate github issue.

Stifler6996 commented 8 years ago

Thanks codekitchen, I have created a new issue #48