A small merit-sending UI tweak

[PowerGlove]

There's a small UI issue with the merit-sending page that makes it easier than it should be to accidentally send more merit than you intended (I'm sure I've run into a handful of anecdotes about this, but I can't find them now).

Basically, the "Merit points" field is pre-populated with a 0, like this:



People are used to having to get rid of that 0 before entering an amount (or, they have to make sure that the amount they enter is after that 0). Sometimes, people are careless or tired, and accidentally enter something on the wrong side of that 0 (maybe believing that they've already deleted or selected it after mis-hitting a key, or something), and they end up sending more merit than they meant to (that is, sending 10, 20, 30, 40 or 50 merits by mistake is an easier thing to do than it should be).

For comparison with what follows, the current HTML for that input looks like this: <input type="text" size="6" name="merits" value="0">.

Here are some ways that I think this could be improved:

Approach A

This approach would leave the field initially empty so that there's no 0 there to trip anyone up.

That would look like this:



The HTML would change to: <input type="text" size="6" name="merits"> (that is, value="0" would be removed).

Approach B

This approach would add a bit of JavaScript that "selects" the value whenever it's clicked, that way, whatever you type in will replace whatever was already there.

That would look like this (after clicking):



The HTML would change to: <input type="text" size="6" name="merits" value="0" onclick="this.select();"> (that is, onclick="this.select();" would be added).

Approach C

This approach would leave the 0 there, but make it "placeholder" text instead of actual text, that way, it's just there as a cue, but the field is actually empty (the 0 will disappear as soon as you type something in).

That would look like this:



The HTML would change to: <input type="text" size="6" name="merits" placeholder="0"> (that is, value="0" would change to placeholder="0").

Closing thoughts

One disadvantage of approach A is that it leaves the user wondering what they're meant to type in (that's obviously not an issue for people that have sent merit before, but I could see brand new users getting confused without any cues to help them).

One disadvantage of approach B is that it requires JavaScript to function, and there's a (pretty small in this case, IMHO) chance that cross-browser weirdness will make it unreliable. One advantage of approach B is that it will catch a wider range of mistakes (sometimes people initially decide to send 1 merit, and then change that to a 2, but actually end up sending 12 or 21, by mistake. If the entire value gets selected each time you click the input, then those kinds of mistakes would be much harder to make).

Approach C won't catch as many mistakes as approach B, but it's simple, won't leave new users confused, and doesn't need JavaScript to work.

I would have included PHP diffs with this post, but I don't have access to the relevant code, so all I can do this time around is make suggestions like a noob.

(I'm taking a break from the forum, but I'll be back on the 27th; try not to miss me too much.)

[1714304169]

1714304169

[1714304169]

1714304169

[1714304169]

1714304169

[1714304169]

1714304169

[philipma1957]

I have sent 10 and 20 credits maybe three times. I would love to see this fix.

[PytagoraZ]

I would have included PHP diffs with this post, but I don't have access to the relevant code, so all I can do this time around is make suggestions like a noob.

I don't know anything about what you're talking about, because the code language is too complicated for me to imagine. So of everything you talk about, I like the word above the most. LOL

Btw, I like option C, hopefully it can be implemented soon, but if not, it's okay because I only have a little merit to send, and often there is nothing to send

[Trawda]

In my opinion, approach A is the most appropriate with some improvements, as it is possible, for example, to add The input placeholder attribute (placeholder="Num 1-99") instead of value="0"

To become as follows:

Code:

<input type="text" size="6" name="merits" placeholder="Num 1-99">

                              

This will solve the problem by giving new users hint to help them enter a correct number between 1-99.

[Husires]

I prefer the approach A, adding the number one instead of leaving the field empty, in addition to a group of buttons next to send that contain 2, 4, 5, 7, 10. if you click on send, you will send one Merit, if you click on the buttons next to it, you will send 2, 4, 5,7,10, and if you want to send more, you must change the number from 1.

img source https://bitcointalk.org/index.php?topic=2833350.msg52249695#msg52249695

[Adbitco]

Approach A

This approach would leave the field initially empty so that there's no 0 there to trip anyone up.

That would look like this:



The HTML would change to: <input type="text" size="6" name="merits"> (that is, value="0" would be removed).

From this I think is more better, this option is pretty cool with me in a sense that the entire body is empty meaning anyone can input any amount of merits s/he needs to send to reduce some common errors.
Hope theymos implement this option..

[cafter]

snip

We are restricted to send only 50merits to one user in a month,

I like the idea of powerglove's Approach C from that any newbie can get the clue, that what the box is for, there no need to write like these 0-50 because these much merits are sent by veterans, even newbie or low rank member don't have that much merits to sent so they will learn about the limits about merits gradually learning more about forum.

[mk4]

+1

I also recommend adding an up/down or plus/minus button so people on mobile wouldn't need to manually type in the numbers. Not much of a big deal, but it's a fairly easy update that could make things a lot less of a hassle.

[Plaguedeath]

Since I'm a lazy person, I support @mk4's suggestion by having "1" number by default because I don't have to input the number to merit someone. Whenever someone want to give more merit, they can click the plus/minus button or input it by themselves.

Although this could raise a same problem someone would mistakenly send "11-19" merits.

[cryptoaddictchie]

I also recommend adding an up/down or plus/minus button so people on mobile wouldn't need to manually type in the numbers.

Good idea but still can implement both of this suggestion and the ability to input manually too. Some people still like to shortcut merit points especially if they giving up so much points to a post.

For me I prefer manually input though. But nice recommendation very convenient too.

[LoyceV]

Approach C

If I get a vote, I vote for this one. But the place holder shouldn't be "0", Trawda's post made me realize "1-50" is better.

(I'm taking a break from the forum, but I'll be back on the 27th; try not to miss me too much.)

Enjoy real life!

This is why I'd like to see this change:

Fork

I was trying to lower my source sMerit balance, and used LoyceMobile's sent Merit history to send those posts some more. With a dozen tabs open, I filled "04" in all of them before clicking "Send" (I have this AI-thing where I try to Merit as much posts in a single second as possible, I've reached 4 posts per second several times). However, I wrapped around to the first tab again, and added another 4 to the existing "04", right before I clicked Send. Long story short: I could see my 44 sMerit transfer to this post, but it was too late to stop it.

I wanted to leave the chain of events here, in case someone questions this transaction later. It's the biggest Fork Up I've had with sMerit
To easy my own mind: the post itself isn't bad, although it doesn't deserve 45 Merits. It's a Newbie who doesn't look like a spammer. So I hope the sMerits trickle down from there to others.
I've Forked Up less than 0.5% of all sMerit I've sent. This was a big Fork Up though

Since I have to empty my source sMerit, I usually send 4 sMerit at a time. I wanted to Merit this post and accidentally clicked left instead of right from the "zero" on the "Merit a post"-page. As some claim I'm AI, I clicked "Send" at the same moment I realized my mistake, and my heart skipped a beat.
That default zero has always been risky, but it's the first time it hit me this hard. Maybe I should send 6 sMerit at a time from now on, so this mistake can't happen anymore.

[FatFork]

I think going with "Approach C" is the most sensible option. Using a placeholder value is a common practice in user interfaces, and it shouldn't create any confusion, even for new members.

[Mia Chloe]

I believe Approach B would be the best if there be need to change the code. The zero in the approach B format should give a clue also to newbies who haven't sent merit before how ever due to this fact by PowerGlove

One disadvantage of approach A is that it leaves the user wondering what they're meant to type in (that's obviously not an issue for people that have sent merit before, but I could see brand new users getting confused without any cues to help them).

I believe it would be necessary to create and pin a thread in the beginners and help section about sending merits to assist newbies in using the merit function

[yhiaali3]

One disadvantage of approach A is that it leaves the user wondering what they're meant to type in (that's obviously not an issue for people that have sent merit before, but I could see brand new users getting confused without any cues to help them).

They all seem like good options to me but I prefer Approach A, with some improvement as mentioned above to give new users hints on the correct numbers to type in the input box.

The best way is to delete the "0", which is often forgotten and causes the wrong merit to be sent, as happened to many members on the forum. At the same time, the hint helps new members.

[shahzadafzal]

There's a small UI issue with the merit-sending page that makes it easier than it should be to accidentally send more merit than you intended (I'm sure I've run into a handful of anecdotes about this, but I can't find them now).
~
Approach B

This approach would add a bit of JavaScript that "selects" the value whenever it's clicked, that way, whatever you type in will replace whatever was already there.

That would look like this (after clicking):



The HTML would change to: <input type="text" size="6" name="merits" value="0" onclick="this.select();"> (that is, onclick="this.select();" would be added).

Have we discussed this before or its a Mandela Effect?

I mean I feel that we have discussed all these approaches change default 0 to 1, leaving it blank or changing it to plus minus button.

Anyway from your proposed option I will prefer Approach B with small tweet changing default 0 to 1, something like



Our most (more than 50%) of merit transactions are 1. For example from most recent 499 merit transactions 314 are 1 merit transactions that's 62%.

So changing default from "0" to "1" will at least favor 62% merit transactions.

I would have included PHP diffs with this post, but I don't have access to the relevant code, so all I can do this time around is make suggestions like a noob.

hahaha I can understand and to be fair these are things preventing theymos from upgrading the forum or switching to Epochtalk smoothly. I think current SMF version has been changed a lot that scares even theymos to touch it. For rexample trust system would be another story.

(I'm taking a break from the forum, but I'll be back on the 27th; try not to miss me too much.)

Last time I predicted for someone going Antarctica, so please tell me are you getting married or going for long honeymoon, of course you don't need to answer

[DYING_S0UL]

We are already missing you.  

Anyway, I prefer Approach C. Short and simple. Just a placeholder text should be enough.

May I suggest another approach?
If you could add a final confirmation message before sending sMerits, that would be nice.

Example: Are you sure you wanna send 50 sMerit to user X?
Yes  No

(I don't know how it could be implemented, maybe throught Javascript I guess)
 

[LoyceV]

If you could add a final confirmation message before sending sMerits, that would nice.

Example: Are you sure you wanna send 50 sMerit to user X?
Yes  No

Please don't!
People will get used to it, and click it without thinking. All in all it would just double the number of clicks required to send sMerit. As the sender of 13734+ sMerit transactions, I don't want to add even a second to each one. That would have been 4 hours already!

[DYING_S0UL]

If you could add a final confirmation message before sending sMerits, that would nice.

Example: Are you sure you wanna send 50 sMerit to user X?
Yes  No

Please don't!
People will get used to it, and click it without thinking. All in all it would just double the number of clicks required to send sMerit. As the sender of 13734+ sMerit transactions, I don't want to add even a second to each one. That would have been 4 hours already!

I didn't thought it like that. I have only sent +- 60 merit my whole life. Yes, for a big merit sender like you, it would only create more problems. We better stick to approach A,B,C then. 

[Upgrade00]

All of the options will be an upgrade to the current system which makes it very easy to slip up and send more merits than you planned to. Although from the rate of merit sent, this is not a issue frequently encountered. I for one have never mistakenly sent out the wrong number of merits, but I guess merit sources will be most affected cause they send merits very frequently and multiple times within a short period.

Option C is the best approach in my opinion.

If I get a vote, I vote for this one. But the place holder shouldn't be "0", Trawda's post made me realize "1-50" is better.

Downside to this is that it gives off the interpretation that one can only send between 1-50 neritsvinna single transaction and not the reality that that's the maximum for a month to a user.

After sending out 10 merits for example at a time and coming back to merit that user on a later date, you have a maximum of 40 to send, but the place holder will still display 1-50.

[Stalker22]

I also prefer Approach C. Just a placeholder text, similar to how it is now, but more error-proof.

hahaha I can understand and to be fair these are things preventing theymos from upgrading the forum or switching to Epochtalk smoothly. I think current SMF version has been changed a lot that scares even theymos to touch it. For rexample trust system would be another story.

I thought EpochTalk was meant to be a completely original platform, not just a fork of some existing open-source solution. So, these features should have been part of its core design from the start, right?

I believe it would be necessary to create and pin a thread in the beginners and help section about sending merits to assist newbies in using the merit function

You are not serious are you?