Hey www,
I always wondered why this bug (or code design flaw) is there at all. Usually when you try to write good code, you try to catch expectable user behaviour. It was clear that this long-known and extremely annoying behaviour could be fixed in firmware. But @Mitch is right, it was on their list now:
So you can look forward to it 