Wednesday, November 05, 2008

chrome's interpretation of notHTTPS

Chrome's pretty sweet. So this will not be an unbiased report or critical assessment of Google's browser.

This page signed its own https certificate, which I believe is not a genuine method of going about https. But I'm glad the department spared the 3 copies of vista it could have cost us otherwise.

So strike-out https, pretty sweet.

Chrome has other tricks I'm crazy about, especially ripping tabs out at any time, and them making their own window. Use case in which I ran in to this today. I was editing a page and it had syntax/aesthetic errors, so I ripped out the rendered page, had the editor open in another, used the "stack windows side-by-side" and worked right through it.

Having the single search bar/address bar, that gives suggested hits from google search suggest, google services (docs, calendar, picasaweb, ...), and browsed history make looking for things especially quicker.

However, there are several caveats, and gotchas to using chrome, the main one is that, you'll still need either IE or firefox as well. The reason is that pages continue to be made that support only a few browsers, and by being new, no web developers are developing pages FOR chrome. The best case would be following web standards, and we're all happy.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.