Comment 16 for bug 833337

I'm not sure that my earlier "simplest fix" position will work: if someone is physically located outside of their custom timezone list, there's no longer an easy way to click-to-set the current timezone from the geo timezone. This regression would certainly be reported & force us to revisit this issue anyway.

After hacking & rehacking this code for the last day, I think I've found a code approach that follows some of the ideas in Javier's second patch wrt removing the special case code, but preserves the older beahvior wrt geo/current location. It improves detection & removal of duplicate entries, and also picks up a fix for Bug #833325 :)