Question

I don't know if this is a problem with Google Chrome or FogBugz or both, but I see the same behaviour in Google Chrome everywhere, yet it's more severe in FogBugz, which leads me to believe that FogBugz is responsible:

When I want to select a field, say the estimated time, and change it real fast, I click on the end, where I have room for error, and slam the mouse over assuming it's mile-wide (a la "mile high" concept Joel Spolsky mentions in "Designing for People Who Have Better Things To Do With Their Lives, Part Two" http://www.joelonsoftware.com/uibook/chapters/fog0000000063.html where menu bars and buttons on the edges are mile high, meaning you don't have to be accurate to use them), but as soon as the mouse is about 20 pixels too far, the selection acts as though I am not even selecting it!! Argh! This is so beyond annoying to have an interface that just flat out ignores your request. If anyone would understand how wrong this is, it would be the Master of U.I., Joel Spolsky.

Can this be corrected? I would like to submit this as a bug report to FogBugz.

Thank you.

Case FC2012887

Answer 1

While Joel is involved in the design of all Fog Creek products, it's a team of engineers and designers who do the actual creation of the software here. If we (or anyone) checked every UI element against every tenet of Joel's in every browser, we'd never get a release out.

This does only happen in Chrome, that I can see. This is a browser quirk that I'll file as a bug. For a more reliable way of selecting all text in a field, try triple-clicking anywhere in the field.