Daily Archives: March 16, 2011

2 posts

Google Updates Chrome Browser Logo

Google has updated the Chrome browser logo with a non-shiny version.

The comes after an all-blue version of the new logo showed up for Chromium, the open-source foundation of Chrome, a week ago.

Google have also updated the Dev channel to 11.0.696.12 for Macintosh, Windows, Linux and Chrome Frame platforms, in which the following bugs were fixed.

New York Times Chrome app crashes on the Chorme Dev Channel (Issue 75563).
Sync login dlg is truncated (Issue 72490 ).
Status bar / target URL not shown when hovering over links(Issue 75268).
Several known crashes (Issues 75171 and 75443 and 75828).
Bookmark focus is not lost when moved away from the bookmark bar (Issue 75367).
Tooltips from browser tabs are persisting for too long (Issue 75334 ).
Content settings updates don’t reflect the current Incognito session(Issue 74466).
NewTabPage is not updating when a new theme is applied (Issue 74311).
fixed download requests in chrome frame which occur in response to top level POSTs (Issue 73985 ).
Chrome locks up on form submit, constantly duplicating autofill settings to blame(Issue 74911).

Dev Channel info: http://dev.chromium.org/getting-involved/dev-channel

Twitter Offers HTTPS Tweet Option

Twitter has added a user setting that lets you always use HTTPS when reading and writing on Twitter.com. Twitter is adopting the encryption protocol, in steps.

For some time, users have been able to use Twitter via HTTPS by going to https://twitter.com. Twitter have made it easier for users to do this by adding the option to always use HTTPS.

To turn on HTTPS, go to your settings and check the box next to “Always use HTTPS,” which is at the bottom of the page.

“There are also a few instances where turning on HTTPS in your settings does not force HTTPS. For example, when accessing Twitter from your mobile browser, you need to go to https://mobile.twitter.com to use HTTPS for now. We are working on a solution that will share the “Always use HTTPS” setting across twitter.com and mobile.twitter.com, so you don’t have to think about which device you’re using when you want to check Twitter. If you use a third-party application, you should check to see if that app offers HTTPS.”

More info: http://blog.twitter.com/2011/03/making-twitter-more-secure-https.html