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 `skipping $num comments` should show for inline preview

Post

`skipping $num comments` should show for inline preview

+3
−0

skipping $num comments should show for inline preview also. I was watching the thread. When I was watching the thread from posts page. Then, I noticed that @ArtOfCode said blah blah blah.......

I was thinking whom he replied. When I saw interested (mention) I thought he was telling something to interested peoples. After reading the comment I realized there was some other comments before that. It was completely confusing. So, I think skipping $num comments should show for inline preview also.

I am not marking it as bug cause, it's status-bydesign.

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

I think this is a bug (2 comments)
I think this is a bug
FoggyFinder‭ wrote about 3 years ago

I am not marking it as bug cause, it's status-bydesign.

I'd remove this sentence since status "by-design" means it won't be changed.

deleted user wrote about 3 years ago

feature-request stands for improving frontend "things". Bug stands for those which was status-bydesign but, they aren't working as expected hence, it's not bug. But, I want the frontend to improve so, it's feature-request.