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 Sorting answers without a page reload

Post

Sorting answers without a page reload

+0
−0

Below a question are buttons for sorting the answers:

The three sorting buttons, Score, Active, and Age

Pressing one of these buttons results in a page reload, with the answers now sorted according to the chosen criterion.

For cases where all of the answers fit on a single page (no pagination links), could these buttons instead sort the answers in place, rather than the user having to wait for a page reload?

Browsers without JavaScript

For users who have disabled JavaScript in their browser, the buttons could fall back to being links that perform the page reload that we have currently, so there is no loss of functionality for these users.

Affected questions

Currently, pagination is added for questions with more than 20 answers, which is rare in most communities, so the majority of questions would benefit from this change. Questions with large numbers of answers are usually only seen in contest categories. For example:

Even there, questions with more than 20 answers are very rare. The only current examples are 6 posts in Challenges in Code Golf.

The only other examples are from communities that imported questions from Stack Exchange:

The highest example, Scientific Speculation, still only has around 10% of its questions having more than 20 answers.

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

Why? (3 comments)
Why?
Olin Lathrop‭ wrote 24 days ago

So it does a page reload. You haven't explained why that's supposed to be bad.

trichoplax‭ wrote 24 days ago

I don't consider it to be bad. I'm not raising a bug but a feature request.

I raise any features I think of, and then people vote up or down to indicate which ones are worth implementing.

One advantage of avoiding the page reload is for people on a slow connection, where it can take several seconds, but even for people on a fast connection the sort would be slightly quicker without having to wait for the server.

Although server load isn't currently a problem, I also like the idea of taking a general approach of only using the server for essentials, so if something can be done without need for server time I'll suggest it for people to discuss.

trichoplax‭ wrote 23 days ago

Just found another benefit. I opened a question page just before going into a long train tunnel. With this feature I would have been able to sort the answers immediately, rather than having to wait several minutes.