[jnevelson]

I tried (again) to switch to FF yesterday when 57 was released, and unfortunately still ran into a known bug that makes it practically unusable for me: FF treats underscores as punctuation that breaks up a word, so given text "foo_bar", if you double click on "foo" or "bar", it doesn't select the entire word. This goes against all conventions of Chrome, other text editors, etc. It seems trivial, but as developers we deal with underscores a lot, and copy text out of our browsers frequently.

There's been a bug open about this for 15 years now: https://bugzilla.mozilla.org/show_bug.cgi?id=196175

[Mandatum]

That's possibly one of their strangest edge-cases I've seen for someone to dismiss a product. Or is this a case of HN-level trolling?

[jnevelson]

Haha. I can see how someone would think I'm trolling, but I assure you I'm not. It's a pretty deeply-ingrained behavior that I perform quite often, so yes, it does make a difference. FF57 is still not so much better than Chrome (to me, anyways) that it's worth dealing with re-learning this for me.

[cannonedhamster]

I don't know, if you develop and are used to being able to click a word or field of text, having to go through and highlight the word is more time consuming and potentially a flow breaker especially when you're talking about variables in some languages.

[cannonedhamster]

I think the worst part of this was that there was a patch to bring this into line with other software and it just got ignored.

[Manishearth]

double click, hold, flick/drag will select the next word. (if you drag-select after double clicking it goes by word not character).