I've had to suffer this rather insufferable file dialog for well over a year now - I don't even know how long I've been putting up with this. NOTHING about this makes sense. If I begin typing the filename, the dialog attempts to guess the path - but instead of letting me CHOOSE the option manually, or fill it via tabbing, it fills it automatically. Why? This behavior doesn't exist anywhere else, and so is completely unexpected. Worse, the user doesn't know when the dialog will suddenly decide to fill, and so has to pause and wait to find out whether the dialog is going to autocomplete or not. Because if they blithely decide to continue typing, they find themselves entering things like /usr/sr/bin or worse. As a final insult, when the user finally DOES get the dialog to fill in the program name, it's often only an apparent result - although it reads /usr/bin/kaffeine, e.g., upon hitting 'ok', the user finds that the dialog has returned /usr/bin/kaf (what was typed before the auto"complete" kicked in), which, of course, doesn't exist.

This bug has probably been filed hundreds of times before, I'm well aware. I don't care. The REAL bug here is that the developers have let this languish for so long. This is one of the WORST file dialog features I have ever encountered, and it is universally despised. I don't know why a team that prides itself on making things that "just work" with "sensible defaults" has let such a terrible state of affairs persist. This needs to be fixed, now. There is no excuse.

Other information: