In addition to the usual ability to “reset to default” should a hijack occur, I believe in this version of Chrome a small window opens at time browser changes, allowing you to both know it happened and immediately reset. For now, it’s become a replacement to me for Firefox, which even “vanilla” has been having problems with many sites…mainstream sites; also, it was crashing instead of closing, or often running in background despite closing.

My only concern is for eventually making it impossible to allow even one instance of Java, Silverlight, et al; I just tried “vanilla” Chrome at some corporate and government sites I know use Silverlight for public info web apps; at some Chrome gave me a constant “wait” wheel in tab bar, but pages functioned normally; I tried with up-to-date IE11, and got the same results minus wait wheel. Should any browser however come to treat all “lazy coding” or Java/Silverlight as if it were de facto malicious, ala Firefox functionality could be lost at some common sites…an impetus for webmasters to do better, perhaps, in a time 74% of sites affected by Heartbleed last year still have the vulnerability, e.g..

Thanks for a great article, hope I said something that matters, cheers to all!