Jason K. Chapman
Jun 15, 2011, 4:43 PM
Post #9 of 9
These, most likely, are all browser-related, even the read/unread issue. The only change to the Speakeasy lately was a tweak to the browser detection function. It was misidentifying Chrome and not allowing the Advanced Editor. I fixed it.
Re: [silkentent] Line Spacing for Posts
[In reply to]
Safari, for what it's worth, causes me so many problems on so many sites I had to stop using it for anything.
The reason I think the read/unread issue could be browser related is that the whole process of keeping track of each user's list is deceptively complex--at least the Speakeasy's code for doing it is. It's all tied in with user sessions, so at one point in the process there's a cookie involved.
The only time I've personally had it lose track of read/unread is when I've been away from the forum for an extended period of time. That leads me to believe that some particular set of circumstances could make it appear that a user has been away when that isn't truly the case.
Eventually, I'll track it down and fix it. I just haven't been able to find it yet.