Live data from Hacker News

Doubleclicking on the Web (2015)

ma.ttias.be

11–20 of 27 posts

Re: Doubleclicking on the Web (2015)

#12
If the client-side solution is so simple, what's the problem? There are many things on the web where, if given a clean slate, it would be nice to change the default behavior. This doesn't seem to rise to the top of that list.

Re: Doubleclicking on the Web (2015)

#13
I've actually heard people verbally use the word "doubleclick" to mean explore. For example, someone in a meeting might mention some idea. Then my colleague would say "let's doubleclick on that for a minute".

Re: Doubleclicking on the Web (2015)

#14
post #4

The proposed solution (an HTML attribute to 'allow' double-click submissions of s) is backwards from how the standard would be updated. The proposal should instead be for an attribute that prevents double-clicks, because that way browsers that have not implemented it still behave correctly. Additionally, you don't "break userspace" for millions of forms online that no longer work as the developer intended. However, I…

And it used to be even better than that before React and JQuery.

`button` worked in the 90s.

Re: Doubleclicking on the Web (2015)

#15
post #13

I've actually heard people verbally use the word "doubleclick" to mean explore. For example, someone in a meeting might mention some idea. Then my colleague would say "let's doubleclick on that for a minute".

I'm going to start using that in my meetings, alongside "drill down", "circle back", and "take it offline".

Office Space became a lot less funny when I started living it.

Re: Doubleclicking on the Web (2015)

#16
post #13

I've actually heard people verbally use the word "doubleclick" to mean explore. For example, someone in a meeting might mention some idea. Then my colleague would say "let's doubleclick on that for a minute".

I'm going to start using that in my meetings, alongside "drill down", "circle back", and "take it offline". Office Space became a lot less funny when I started living it.

Looks like someone has a case of the mondays ;)

Re: Doubleclicking on the Web (2015)

#18
Interestingly, the only persons I've ever seen doubleclicking in the web are from my parent generation (>60, >70 years old).

Also since 2015 the mobile adaption increased more and more. On mobile devices, the "double tap" concept never was very important, I think (at least not in the web context).

Therefore my feeling is that this issue is mostly a thing from the past.

Nevertheless I sometimes see forms which implement this "disable after submission" principle. Especially when it's about money, such as when booking a hotel or flight, etc.

Re: Doubleclicking on the Web (2015)

#19
post #10

If you want a better server-side solution, you could try employing mandatory idempotency tokens in the request payload. The concept is simple: either have the server give the client an idempotency token as part of the page load, or have the client request one at some point, or have it be something that can be generated on the client side (nonce style) and send it with the request. The server can then validate, using…

CSRF tokens solve this problem for free
Post reply on HN