HTML5, CSS3, and ECMAScript are all standards that don't change very frequently. Not all browsers support them equally, but I thought we were trying to get away from caring about that. I haven't seen a "this site is designed for X" (X being some browser, usually IE or Netscape back when this practice was popular) badge in quite a few years. To me it seems that this strong competition amongst browser developers to compete for features and updates has been influencing web developers to bring back this bygone era. Is that really where web developers want to go again?
"Fragmentation" to me isn't an issue. A user shouldn't have to trust your code implicitly always and forever. If they don't want your shiny new features, they should be able to download an earlier version and stick with it.
Also, as mentioned elsewhere -- distro's might take issue with this sort of scheme.
To me it seems more like a competition with Chrome than a technical choice.
For reference (according to that page), here are the numbers for each browser & version listed (as a percentage of that browser's share), along with the stable release date (from Wikipedia) for that version:
IE8: 65.3% - 3/19/09
IE7: 24.9% - 10/18/06
IE6: 9.8% - 8/27/01
FF4: 2.3% - x/x/11
FF3.6: 85.3% - 1/21/10
FF3.5: 8.2% - 6/30/09
FF3: 4.2% - 6/17/08
Safari 5: 84.2% - 6/17/10
Safari 4: 15.8% - 6/8/09
Chrome 8: 100.0% - 12/2/10
Firefox 3.6 has been out over one year and, according to those stats, there are still ~13% of users who are using earlier versions. If Firefox 4-7 are released in 2011, without automatic updates, it would stand to reason that fragmentation could increase.
“Firefox 5.0 (which will be out not long after 4.0) will have completely transparent addon updating - not even a dialog box.”
Extensions you install using Firefox are kept locally, on Linux in your ~/.mozilla/firefox-{version}/{profile}/extensions/ folder. This is the only part that is intended to be self-updated and there is nothing preventing that.