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 Implement duplicate up-down vote buttons

Parent

Implement duplicate up-down vote buttons

+4
−2

I would like to have a smaller pair of duplicate UP and Down vote buttons at the end of a answer or question so I can vote after I have read it. I do not want to scroll up to vote especially if there is only one answer and I do not need to read further to make my vote.

Such 'advanced' features can be small and even configurable. A pop-up could indicate that they can be hidden if they are bothersome. After 6 months the majority selection by active users could be used to determine the default status.

EDIT: I would always prefer features that use less scripting. I like to browse with third party script loading off when first visiting a site and it would be cool if features would fall back for such users. So a no script way to achieve a floating button cluster would be ideal.

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

General comments (1 comment)
Post
+6
−0

For the buttons, I propose something bolder: don't duplicate them, move them. The logical time to make a voting decision is when you've read a post, so I agree they belong at the bottom. But why have them at the top?

Currently we bundle the reporting of existing votes and the voting buttons together, but we don't have to. We could find a way to show existing votes at the top but have the buttons to cast votes at the bottom. Why do they need to go together?

(I agree with the suggestion in a comment to break this into two posts, so I'm addressing the one in your title but not the other issue you raised.)

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

1 comment thread

General comments (2 comments)
General comments
KalleMP‭ wrote about 4 years ago

I posted a comment but it did not stick, not sure if I have enough cred. The floating idea same as posted in other answer would be ideal but I fear the scripting cost. If it can be done with styling or HTML code then that would be ideal. Sometimes you will want to vote from the top because you read all the answers and have returned to the top and want to vote on the first answer having to find the end would be unneeded work (unless fast navigation).

Monica Cellio‭ wrote about 4 years ago

@KalleMP‭ I don't see a comment from you (even deleted). Is it possible you clicked the "discard" button instead of the "post" button?