Well, yes, and no. It's still something that the browser has some control over (by controlling what it sends to the server). The main one that bugs me is actually Google Apps themselves. I wish Google would give me the choice whether I want their browser to be displaying mobile vs 'real'. Maybe even on an application by application basis. It would be as simple as altering what's in the string the browser sends the server ... something like "android-webkit-mobile" vs "android-webkit-normal" or something.

But even with that said, I have noticed that there are some sites that do mess with the android browser (not in the way you mean, but in the "the browser isn't up to the task" way). I think it might be that the browser isn't a fully Ajax capable browser. It probably makes UI, memory-footprint, and cpu-power compromises that are appropriate for a phone ... but may not be appropriate for a netbook/tablet (meaning mid-range size tablet, not MID/NIT size tablet).

All of that says to me that it might be easiest done, on mid-range devices with Android, with two browsers -- the default android browser, and a more conventional browser (Chrome? a port of Firefox?), and have a menu option on both browsers that says "open this in (the other browser)".