Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Comments on Notification dropdown sometimes doesn't open when clicked

Post

Notification dropdown sometimes doesn't open when clicked

+2
−0

This has been a recurring problem for me.

Sometimes (far from always, but far too often to be comfortable), when I click the notification dropdown "inbox" icon, it simply fails to open; the element is selected (a dotted line is drawn surrounding it) but nothing else happens. This is on Firefox ESR (currently) 68.12.0 64-bit on Debian, but I've had the same problem for a while so it's not tied to the exact browser version.

It's a bit difficult to pinpoint since it only happens sometimes. What I can say is that I'm not changing any settings in the browser (either the browser itself, or plugins) between when it works and when it doesn't.

I have looked in the browser's Console and Network tab, and things look fine there; a XHR POST is issued to https://meta.codidact.com/notifications/read_all when I click the inbox icon, and that responds with HTTP 200 and response body payload {"status":"success"} (but curiosly, apparently no message data) and there are no relevant failures shown under Network despite "Persist Logs" being on and "All" requests being selected to be shown. That request includes the __cfduid cookie with what looks like the same value as a request to load a question page (which definitely shows me as signed in), and there seem to be no other cookies involved in either request.

The only possible partial explanation I can think of is that I am accessing Codidact over Tor, but the fact that there are no relevant errors shown in the browser's debugging tools seems to suggest that this is not the problem. (Please don't say "don't use Tor". Being able to access a site over Tor can be a major issue for privacy-conscious users, and shouldn't in itself cause problems on a well-designed site.)

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

General comments (7 comments)
General comments

Please don't say "don't use Tor" hell I wouldnt mind if you had even created a tor tag

Moshi‭ wrote over 3 years ago

Could it be related to this issue? https://github.com/codidact/qpixel/issues/162

(Despite being closed, it hasn't actually been fixed yet)

Zerotime‭ wrote over 3 years ago

I can reproduce this: I can't access the comments on any questions and answers I browse. Firefox, Windows 10.

Lundin‭ wrote over 3 years ago

I have this bug too in Firefox. Very easy to reproduce: reload the whole site such as meta.codidact.com, click on inbox - dropdown appears. Click on a post to open it, then click on the inbox. The dropdown is now broken. If you refresh the page, the bug disappears.

Canina‭ wrote over 3 years ago · edited over 3 years ago

@Lundin Thank you! That doesn't solve the problem, and I still think this needs to be fixed, but only opening the dropdown from the index page does seem to at least be a solid workaround.

Trilarion‭ wrote over 2 years ago

Is the issue still happening? If not, maybe it was fixed in the mean time and stats-completed could be added.

Canina‭ wrote over 2 years ago

Trilarion‭ Good point. I don't think I have encountered this issue in a while, so maybe it did get fixed at some point.