Babble not working on ipads

Hi,

There seems to be a general problem with Babble not working for our users on ipads:

http://forum.stockingshq.com/index.php?/topic/42862-chat-room/

Any thoughts?

Best wishes and many thanks!

David

which browser?

Changed Status from Pending to Work in Progress

okay i tested on my ipad (it is a mini2, so its a fair bit older) on safari and chrome (latest versions and latest iOS). safari hangs for about 20 seconds, but will load and work fine. 

Good point. I assumed Safari, but I just tested on mine and it seemed okay apart from the user list - screenshot attached. I'll follow up on the thread and ask them.

Mine is an iPad mini 4. I'll find out which versions etc... Sorry - I should have done that first.

1 minute ago, DBSHQ said:

Good point. I assumed Safari, but I just tested on mine and it seemed okay apart from the user list - screenshot attached. I'll follow up on the thread and ask them.

this is a issue with mobile browsers in general, it doesn't honor the min-height of the window for some reason, but it doesn't really effect the performance and it will honor the "max-height" so the scroll will eventually appear. I'm working on 2.8 which has several elements being redesigned and the online list is one of 'em, so hopefully 2.8 fixes this issue in particular. 

Excellent news. I've posted a message in our forums to see if there's more information, but I think it may just be a case of waiting longer for it to load.

They're all still absolutely ecstatic with Babble though - they absolutely love it!

D

3 minutes ago, DBSHQ said:

Mine is an iPad mini 4. I'll find out which versions etc... Sorry - I should have done that first.

i don't think the ipad version matters, unless it's like the ones apple no longer supports with the latest iOS, not sure if jailbroken status effects anything. some dev's claim it does others says it doesn't, i however can't say if it has any effect on it all as i've never jailbroken my ipad or known any one who has had an issue and that being the case .  just which browser they are using should suffice, and see if waiting about 10 to 20 seconds (as the websocket upgrade process can be a bit cpu intensive, so on older devices it might struggle a bit). 

Changed Status from Work in Progress to No Response