You are reading a single comment by @Velocio and its replies.
Click here to read the full conversation.
-
Seems a reasonable fix. Given that you ideally want to expose an API then it makes sense to replace the anchor-based scrolling with a query string based one. It also makes it easier to implement posts-per-page options in the query string. You could even replace the single post permlinks with ones that kept the requested post in its thread context.
Ah, found it.
It's a WebKit bug that Chrome independently fixed in their version but Apple have not: https://bugs.webkit.org/show_bug.cgi?id=24175
If a redirect occurs, then Safari discards the anchor.
I have an idea for a fix, to copy the anchor into the querystring and then to have JavaScript check for it... and if it exists jump to that part of the page. But it might be messy and involve a reload or will insert things into the browser history. I'll check before I do it.