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

Post

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)
Further details
trichoplax‭ wrote over 1 year ago

Thank you for raising this. There has recently been a fix for the problem you describe, so it seems we have missed a way that this can happen.

To help investigate what needs to be fixed, do you remember any details about where the comment was being posted? For example, do you know which post or comment thread you were trying to post a comment in? If not, it would still be helpful to know whether it was a question, answer, or comment thread.

peterh‭ wrote over 1 year ago

Yes, I have commented this question. The comment was long, and afaik it had also some formatting markups. Note I am using a firefox on Linux with a lot extensions, although javascript instability happens rarely by me, it is a possible problem source. I might try to reproduce it. But I think it is not a client side problem. I have also clicked "start a new comment thread". Nothing warned me that I should not.

peterh‭ wrote over 1 year ago

trichoplax‭ Wow! I have got the "participate everywhere" ability, yet the problem still exists.

trichoplax‭ wrote over 1 year ago

Thank you for the additional information. If I've understood correctly, you were incorrectly shown the option to:

  • Add a comment to an existing comment thread under a question by another user.
  • Start a new comment thread under a question by another user.

Neither option should be displayed to you until you have gained the ability to post comments there, so we will look into this. I agree it is unlikely to be a client side problem. The intention is that the site should work even with JavaScript disabled.

I'm sorry that this wasted the time you spent writing your comment. Thank you for helping narrow down the bug.

trichoplax‭ wrote over 1 year ago

I didn't see your message from 5 minutes ago until after pressing send.

At first that sounds like a different bug, but it's because you have "Participate Everywhere" here on Meta (where you can comment). On Software Development you only have "Participate", which restricts where you can comment. See the difference between your profile pages on the two communities:

Hopefully this explains the difference in where you can comment between the two communities (although letting you try to comment where you can't is still a bug we need to look into).

However, having said this, it now occurs to me that the name "Participate Everywhere" is misleading. It means "everywhere on that community", but "everywhere" might naturally be assumed to mean all communities. I'll recommend renaming that to be unambiguous.

peterh‭ wrote over 1 year ago · edited over 1 year ago

Ok my please. Another fun: now I could comment here: https://physics.codidact.com/posts/288288 Note that I registered physics codidact only after I have got the "participate everywhere" ability.

trichoplax‭ wrote over 1 year ago

That's due to a difference in the way different communities treat abilities for new users. The natural state of a community is that a new user only gets "Participate" at first, and earns "Participate Everywhere" later. However, since most communities are still small, new users are given "Participate Everywhere" immediately. Only a few larger communities like Software Development make new users wait for "Participate Everywhere". Meta and Physics both give new users this ability immediately.

trichoplax‭ wrote over 1 year ago

I've raised Ambiguous ability name to see if someone can think of a clearer name.

peterh‭ wrote over 1 year ago

Okay. Now, "Participate Everywhere" means that I can write comments on all the sites, or that I can write comments on the all the posts, but only on the site I have got it? I am a total newbie to this part of the system. My first thought was that "Everywhere" means here all the sites, and not only all the posts (of the current site).

trichoplax‭ wrote over 1 year ago

I agree that is confusing, so I raised a new Meta post to change it to a less confusing name.

To clarify: "Participate Everywhere" only means everywhere on that one community. So you currently have Participate Everywhere on Meta and Physics, but not on Software Development.