False logic. The only way to address the problem at its root is by getting Google to change a couple of lines of Javascript on their end. They will not do this without pressure. By "fixing" end users one at a time you are reducing the complaint level to Google, thereby delaying or preventing them from acquiring sufficient momentum to "fix" the problem.
Of course, if they do "fix" the problem then you'll be complaining about top-posting, and if Google makes the cursor start at the bottom, you'll be complaining about insufficient quote trimming.
By the way, you'll note that I use Google, nee dejanews. I don't have NNTP access from most of the locations where I sit when I'm posting. Those locations that do have news servers have different news servers. I can't access my home ISP's server from school, I can't access school's server from home. It would be an unreasonable burden of screwing around with profiles and accounts to lash together a set of configurations for all of the different locations where I have NNTP access - and I'm SOL at work and a couple of other places that simply have no NNTP at all. I'm certainly not paying an additional monthly subscription for a third-party server. Free web-front-end access like Google gets through all the firewalls and gives me a consistent access method no matter where I'm sitting.