iPhone browser problems today?

[BigT]

@snowthx

Yeah, I saw that but skipped over it since I do not use an Apple device or Safari.

@gnoitall

Short answer: a planned end-of-life change in Discourse which apparently just took effect. Discourse code checks for browser version when you connect and if the browser has been designated as “out-of-date”, Discourse displays a non-Javascript view. ⁢

Thanks - this makes sense. Odd thing is this happened about a year ago on my very old Kindle Fire and I remember trying to resolve it by installing a new browser, but was unsuccessful (as I am now). But, a few days later, SDMB was working again, and had since, until the other day. ⁢

There have been a few cases where they accidentally made changes that broke compatibility older iOS versions and only fixed them after people complained.

As for getting another browser on your Kindle Fire, you probably need to look for an APK for Firefox or Chrome on a site like apkmirror.com. Though if your device is actually a Kindle Fire (i.e. from 2013 or earlier), you may not be able to install a new enough browser.

[snowthx]

Yep, I think that is the case (2013 version). I installed the APK files for Play Store (to install Chrome) this morning from that site, but now my Kindle wont open them up to install (parsing error). I am thinking the gig is up for the SDMB on my device. I may try again for Firefox if I have time.

[Mean_Mr.Mustard]

I had the same issue (iphone 13, ios 16.11, Safari).

I said, “huh!” and downloaded Microsoft Edge. That was yesterday.

Today, Safari is working normally with SDMB.

So, again, I said, “huh!”.

mmm