Live data from Hacker News

Doubleclicking on the Web (2015)

ma.ttias.be

21–27 of 27 posts

Re: Doubleclicking on the Web (2015)

#21
post #2

This is something I usually take care of by throttling the relevant event listeners (in an AJAXed site) but the way this article puts it makes me wonder if this is as easy as globally disabling double clicks on links and buttons: document.addEventListener('dblclick', event => { if (event.target.closest('a, input, button')) event.preventDefault() })

Would be careful with this (if it works), double clicking can be used to select text, which might turn out to be annoying when disabled in non-button inputs - certainly on mobile I use it a lot.

Re: Doubleclicking on the Web (2015)

#22
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…

Except that for the overwhelming majority (admittedly not literally all) of those forms, no-double-click is how the developer intended them to work. If anything, I call [citation needed] on the implication that there is any anywhere that actually expects or relies on double-clicks producing two different HTTP requests.

Re: Doubleclicking on the Web (2015)

#23
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.

My person pet peeve jargon is people who use surface in sentences like "what ideas does this surface?"

Unless you're a submarine, surface isn't a verb!

Re: Doubleclicking on the Web (2015)

#25
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

AFAIK typical CSRF token implementations allow for reuse, and unlike an idempotency token necessarily need to be generated by a trusted server. They solve a different problem.

Re: Doubleclicking on the Web (2015)

#26
post #24
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".

Wow, that's truly awful.

It gets worse.

Where I am people use "doubleclick" and "tripleclick" as nouns to represent specific levels of detail. As in, "I think we've got a good story for the doubleclick but I want to hear more about the tripleclick on Topic X."

Re: Doubleclicking on the Web (2015)

#27

Earlier quoted context omitted.

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.

My person pet peeve jargon is people who use surface in sentences like "what ideas does this surface?" Unless you're a submarine, surface isn't a verb!

That's pretty common, there are 53,000 results for "surfaced a problem":

https://www.google.com/search?q="surfaced+a+problem"

Post reply on HN