RE: Secure Chrome

Lets break the problem down.

Secure Chrome has a number of attributes:

* Must be recognizable as secure chrome to the user
* Must be under exclusive control of the application
* [Possibly more]

There are a number of ways that secure chrome might be achieved and a number
of degrees of security possible:

* Secure Chrome - security guaranteed by the operating system
* Spoof resistant chrome - security guaranteed by application level best
effort

Adding the Google toolbar is an unintentional but effective protection
against many phishing attacks spoofing the address bar in javascript because
it mucks up their pixel counts. 

Refusing to create frameless pop ups. Rejecting the idiotic notion that the
content provider has the right to determine the end user experience does a
lot.

To get to absolutely secure chrome we are going to need close coupling to
the O/S security layer. But this is a goal to work towards not a must
achieve first day requirement.