and other mobile devices. I can still get on at my local library as well as my pubs public computer. But if I borrow a freinds smart phone or tablet its a no go. My user name and password wont go thru.
Which smartphone or tablet are you using? Sometimes we find there are issues with a newly updated OS. If you can pass along that information, I can pass it along to our IS people.
Verison ?
I don't know if he is trying to say 'version' as in software or device or 'Verizon' as in carrier, but would suspect the former.
As for me, on an iPhone 5s running iOS 11.1.2, the 'mobile experience' has more bugs than an Alphabet City apartment with peanut butter smeared on the walls. I would list them in detail but, since I am posting from the device in question, it might take me too many frustrating hours to do all the text entry.
I would cheerfully do this via PM, for instance, but I find the mobile instantiation forbids me from accessing my own messages; going to the full site view with the helpfully-provided button lets me see the list, but responding with the phone vertical makes most of the reply scroll to invisible and unresizable regions of the screen, and rotating the device horizontal provides a two-line-high entry window that does not stay scrolled down to the entry point for any reply longer than a tweet. Fortunately a very small edge of the 'reply' button can actually be found and clicked (if not doing text entry) with the phone horizontal, so I can more or less blind type-ahead vertically and then rotate to send, but the result ain't Shakespearean and of course there's no edit facility.
I am making up a list of the issues and will send it when I get to a device that can access the site coherently, but that may take some time - please be patient.
The intolerability has been present since the introduction of iOS 11; there has also been a disaster with text entry on the device itself perhaps comparable to the Apple Maps fiasco in that all the text-entry logic seems to have been fouled up when they introduced controls in Keyboards to allow more granular selection of entry features. I expect it will take them the usual crApple path of denial and you're-holding-it-wrong sanctimoniousness to actually get the control suite to, say, '80s-level IxD ... but it's at least possible that other parameters passed from text entry or display in iOS 11 are sending the Kalmbach codebase information it cannot parse correctly as designed for probably much older versions of iOS.
Our community is FREE to join. To participate you must either login or register for an account.