update-alternatives and the Chrome takeover quash

Finally got round to understanding Ubuntu's /etc/alternatives a little more after installing Chrome made it my default browser!?  More details after the jump (another first!) but briefly:

• List all alternative-able things:

  sudo update-alternatives --get-selections

• Choose which browser:
  (these present menu to select from)

  sudo update-alternatives --config x-www-browser
  sudo update-alternatives --config gnome-www-browser

Checking Chrome's postinst script, the Chrome developers thought it was a dodgy thing to do, too.  They comment (below) that Firefox has too low a priority so concluded:

# /usr/bin/google-chrome 200
# /usr/bin/galeon 120
# /usr/bin/konqueror 100
# /usr/bin/seamonkey 80
# /usr/bin/firefox-3.0 40
# /usr/bin/firefox-2 30

Love when you get to see bit-company's developers' humanity (what I wouldn't have done back in the day to perceive IBM as human!).  The script includes edited comments:

This is all pretty insane, and the Debian policy manual does not have clear guidelines. While these values should really be keyed off the most popular browser (Firefox), in practice, the most insane setting probably needs to become the lower bound (hi, Galeon), so let's go with the following scheme:
...
Anyone want to poke Firefox to raise their priority?

Wonder whether the Firefoxes have read this?  What's that?  It's open-source so I should [damn well] do it myself?  Fair. Reminds me I must resume using RTM!
:-)