At least it is fixed in 2.2, but as of right now 2.1 still has a slight lead over 2.2 in terms of userbase (it should be noted that no devices currently use 2.0 anymore). Hopefully more devices will get pushed from 2.1 to Froyo, or maybe now directly to Gingerbread (2.3). At the very least, if the manufacturers don't plan on upgrading their devices past 2.1, they can at least issue a fix for the browser itself.

In fact, issues like this may be a sign it is time for Google to break the Browser out of the main OS like they have recently done with the GMail and YouTube apps. By separating the application from the core OS, Google is able to remotely upgrade that specific application without having to get the vendors to issue a whole new firmware upgrade.

Maybe, there are no devices shipping with 2.0, but 1.6 (and, I think, even more tragically, 1.5) are still shipping. And I can't really see definitive information on how far back this bug actually goes.

Worse still, when a phone ships with an OS, it often keeps that OS version for all of its life. A few get some kind of third party mod to a more recent OS version, and some get a manufacturer/provider upgrade, but, as far as I can tell, this remains a minority sport.

Now, that would be a really good idea that Google should adopt. Not doing it encourages people to use third party browsers, which seems to undermine any gain Google get from the whole Android business.