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 "town hall" (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 Please warn that I can not comment before I write the comment

Parent

Please warn that I can not comment before I write the comment

+6
−0

As a new user, I can only comment in certain places.

But please, I would like to know it right before I start to write the comment.

The current behavior of the software is that it swallows my comment and I get the notice box only after that. This way my work invested into the writing in the comment is lost.

History

1 comment thread

Further details (10 comments)
Post
+1
−0

You'll be happy to know that this has a completed GitHub issue but maybe isn't deployed yet.

Edit: It was deployed after all. This bug is new. See comment thread.

History

1 comment thread

Seems to be a new bug (3 comments)
Seems to be a new bug
trichoplax‭ wrote over 1 year ago

Although a fix was merged for a similar problem, that has already been deployed, so it seems there is another way this can happen that hasn't been covered yet, or the bug has been reintroduced somehow.

Michael‭ wrote over 1 year ago

Thanks. I did not realize.

trichoplax‭ wrote over 1 year ago

There is a new pull request https://github.com/codidact/qpixel/pull/1647 pending approval and deployment.

Skipping 1 deleted comment.