As a side effect of the e-mail provider change, I updated the discourse installation to 2.4.0 beta4. I don’t know if it’s intended to resolve any of the issues you’ve been seeing, but please take a look and see if it helps at all.
Dunno if it’s a bug, but I now have a banner asking if I want to install Elsewhere on my device.
That’s apparently a new feature of beta3:
It shouldn’t ask more than once if you dismiss it. Let me know if it’s annoying and I’ll look into disabling it.
There’s been a change that I really dislike. I used to be able to select a word or abbreviation (that I didn’t understand) from a comment, and have two choices: I could press the quote button (because I wanted to respond), or I could right click my mouse to get the context menu, then copy or search Google or whatever. Now, the second choice doesn’t appear. It’s Firefox 69.0.2, on Windows 10. I have NoScript on Trusted for this site. I’ve restarted Firefox, and it’s still this way.
EDIT: See below:
I wonder if this has anything to do with a mobile-first approach. I’ve noticed in the latest Twitter UI, right-click is treated as a regular click in many cases (very annoyingly). And on a couple of online sales sites I’ve been to recently, the same thing happens. And on Facebook Marketplace. (Even though I’m on desktop.)
@tekna and everyone –
OOOPS. My bad. My right mouse button is not working!!! I haven’t been doing much, clearly, so didn’t notice. So pls IGNORE my post above!
It seems to be session related for me; I’ve got two posts in Not Feminism 101, two in Our so-called president, and one in The Nazification of the World, that won’t mark as read, no matter how many times I click back and forth between them. In the past, closing out of Chrome entirely fixed it.
Edit: yep, new Chrome session fixed it.
Hm. For me it seems to be speed-related. On data posts hardly ever get marked as read; on wifi they often but not always do.
I’ve been trying the “clear Chrome” thing and it seems to be working.
That does not explain why it doesn’t work when I’m in my laptop, in which case it’s almost always a new version of Chrome.
Is ironic that this thread is now that thread that won’t show as read for me?
Not in the classic ironic, but perhaps more of a “fly in Chardonnay” ironic I suppose.
It’s definitely getting worse. I can’t even clear cookies and cache then reload and log back in to fix it.
This is leading to a lot of rereading and confusion.
I’ll definitely need to run in-depth regression testing. Was not able to replicate issue as described on Windows 10, Firefox/Chrome/Brave.
It definitely affects me more on mobile; I think @gadgetgirl is right about the instigator being connection-related somehow.
It effects me on Brave, on both a data connection and wifi.
If I comment, it marks as read. No other interactions will do the same,
I can also confirm that it is not Discourse-wide, because it is not happening on the other place.
For folks having the issue, what does your browser history look like when you scroll through unread posts on a thread?
Mine shows an entry for each post, like so:
I imagine there’s some sort of javascript callback as each post scrolls into view, so if it is a connection speed and/or device-related issue, it could be something like the “I read this post” requests timing out, or otherwise not quite making it back to the server. That’s pure speculation on my part (it’s been a long time since I’ve done any web development), but it seems at least mildly plausible.
I’ve been seeing strange behavior where in the list of topics it says it was updated 3 or 4 days ago but when I go in the last post was from weeks or months ago. I didn’t notice this and ended up necroing some old threads. (Not that there’s anything wrong with that.)
Welp, it started doing that to me today on mobile (Brave browser) so I can confirm that the issue exists, but not a clue as to the why
Edit:
changing session seemed to work!
I needed to clear my cookies and relogin to eleswhere.cafe-- before I cleared cookies, the site displayyed as a blank screen.
running Safari Version 13.0.2 (14608.2.40.1.2) on macosx10.14.6