For the last few months or so the reader view in safari isn't loading the next pages/chapters for the story. I have to exit out of it and scroll to the bottom to get to the next page/chapter. It doesn't happen to me on other sites do not sure what's going on. Any help would be appreciated thanks.
sounds like either a cookie or scripting issue, try clearing your cookies and cache, and if that doesn't work check if you have something interfering with the site's javascripts.
I didn't change anything in the linking scheme for chapters/pages for years now. Something must have changed in safari's algorithm and it's not figuring out what to load next. For something reason it's not even picking up the 'next' 'prev' navigation links in the header that are designed for accessibility.
There is nothing for me to do about that. It's a safari problem.
There is nothing for me to do about that. It's a safari problem.
This behavior is consistent in Safari Technology Preview, which is version 12 (the current release is version 11). Whatever it is, seems to be consistent, which leads me to believe they changed something as you suggest.
I don't use 'reader' view on Safari very often, so if someone can tell me what OUGHT to show up, I could use my developer account to file a bug report.
I could use my developer account
Safari is the Satan's spawn of browsers. I feel great distress that you are trying to work with/around it.
Safari is the Satan's spawn of browsers
To each their own. It's my browser of choice.
But out of curiosity, since I run the site and should be aware of readers choices, why do you think that of Safari, and what is your browser of choice?
It used to be that when you coded you targeted webkit took you 2 hours then you had to add workaround code.
It took about 4 hour to make it work in IE and 1 hour for firefox, the rest Opera etc was "degraded" and nobody cared.
Nowdays, we target the web standard it only took 1 hour (instead of 2) and it works on Edge, chrome, Firefox.
Then we workaround safari bugs for 5 hours...
It's more like safari has becomes the former new Internet Explorer:
- Non standard compliant.
- Buggy.
- Much harder to debug than the competition.
A few year back Safari was on par or better than Chrome and Firefox. Today, it has aged badly, the devloppement has staled, it lack tons of bug corrections, and new features.
To the point that even Microsoft Edge is faster and more stable than Safari...
Obviously, that's a dev perspective, I'm not sure if the lack of standard compliance is an End User issue.
It's more like safari has becomes the former new Internet Explorer:
Could be. For me it's been fairly consistent. As I use safari as my browser, I develop using it and the resulting code works well enough on other browsers. Of course, not relying on Javascript too much, keeps things simple and not too cumbersome to do.
A few year back Safari was on par or better than Chrome and Firefox. Today, it has aged badly, the devloppement has staled, it lack tons of bug corrections, and new features.
To the point that even Microsoft Edge is faster and more stable than Safari...
You should try Safari Technology Preview. It's stable, and contains significant improvements and new features.
https://developer.apple.com/safari/technology-preview/
and what is your browser of choice?
I don't think anything of Safari, I've never tried it. My browser of choice is FireFox.
what is your browser of choice?
I have to say, these days it's Chrome. It used to be Firefox, but that was some time ago. (I just checked, and I don't even have Firefox installed at this time.)
The major reason I shifted from Firefox was when they had an upgrade that incapacitated the majority of my installed extensions, and then that kept happening time and again, so I said "bleep this bleep, I'm outta here!"
My secondary browser is Microsoft Edge. There have been times when things have gone weird on my system and I'll experience problems with Chrome that don't replicate with Edge, so it's my backup while I figure out just what's gone weird inside my computer's software interactions. Of course, there's also that Chrome doesn't want to allow me to download Youtube videos using a browser extension... which is not unreasonable given that both are submarkets of Google, and Google isn't going to allow it's various submarkets to adversely affect the revenue streams of the other submarkets. Microsoft has no such concerns about _Google's_ submarkets, so it allows extensions to Edge that can download videos from Youtube.
I must admit, one of the selling points with both of these browsers is that your settings, once you have signed in, sync between your various machines. Which does require them to be stored by the browser provider; if you don't trust the firm that produces the browser, this would _not_ be a selling point.
Both of them, I will concede, have made changes to your ability to tweak their settings that actually make it harder to do things that I like to do to customize my experience than it used to be. So far it hasn't aggravated me to the extent that I've actively started looking for an alternative again.
I must say that my opinion was forged some years ago, and I was so burned by it that my opinion lingers on. I write specialised web based software (not just web pages), and I have no dramas dealing with all the other common browsers, but Safari had/has their own peculiar take on some html and javascript 'standards' and caused me no end of grief. The version running on iPads, for instance, just simply didn't implement some javascript, and also seemed to 'transparent proxy' a lot of content.
Anyway, these days I tend to use Chrome or Firefox, but still have to test on them all (sigh).
I don't use 'reader' view on Safari very often, so if someone can tell me what OUGHT to show up, I could use my developer account to file a bug report.
The reader view is designed to remove distractions from modern we pages like ads and other annoyances. Basically, it renders most articles on other sites like the story view on SOL/FS/SFS.
It has an additional 'feature' which OP was missing. When you click on a story/article that has multiple pages, the browser finds the links to the next part and loads it as a 'page' in the window. So if you have a story on SOL, you click chapter 1, and then click the reader view, and safari loads all the chapters in the window.
It still works with some of the other sites that I visit. I didn't know that it stopped working that way with SOL until OP mentioned it.