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 No escape from reactions dialogue box

Parent

No escape from reactions dialogue box

+1
−0

I clicked on "react" on an answer on Codidact Meta and found that the only available reaction is "Outdated", which I don't want to use. There doesn't appear to be any way to close the dialogue box without adding a reaction, other than refreshing the page. There is no obvious close button and clicking on other parts of the page leaves the box open. Pressing escape also leaves the box open.

reactions dialogue box with no close button

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

1 comment thread

How to close the react box (3 comments)
Post
+2
−0

Since this question was posted, the user interface has been updated so that clicking outside a pop up panel makes the panel disappear. This means a new user unfamiliar with the site will now be able to dismiss panels easily, so this is no longer a problem.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

testing a different bug (3 comments)
testing a different bug
Monica Cellio‭ wrote almost 2 years ago

Hi. I want to test this bug without bothering anybody else. Could you reply to this comment? Thanks.

trichoplax‭ wrote almost 2 years ago

I initially tested this with a couple of previous (already read) notifications, without first marking them unread. I've now used your notification from this comment thread to test with an unread notification (first navigating to this thread page manually, and only then clicking on the unread notification that links to this same page). I still see the same behaviour (panel stays open until I click elsewhere on the page). This depends on the initial page being this comment page (not the question or answer page that the comment thread is a child of).

Here's a ping so you can see if it still differs on your machine.

Have you also tried with a notification that is already read (without marking it unread) for comparison?

Monica Cellio‭ wrote almost 2 years ago

Ah! I must have done something wrong before; I'm now seeing the behavior you're reporting.