News for hackers. Stuff that matters.
Re:Chrome 14 released by samstokes on Friday September 16, 2011 @01:33PM (#3005413)
This release includes another significant change that, for some reason, neither the submitted article nor the higher-level announcement [1] mentions: if an HTTPS page loads a script over HTTP, the script is now blocked from executing. There's a popup which warns you that "This page has insecure content", and you can opt to ignore the warning and unblock.

[1] http://chrome.blogspot.com/2011/09/new-stable-release-of-chr...

Re:Chrome 14 released by stanleydrew on Friday September 16, 2011 @01:59PM (#3005529)
This was covered a little while back. [1][2]

Still worthy of mention though. I personally love this change. I am on the dev channel (15.0.874.5) and I think insecure content is just blocked by default, without a dialog.

[1] http://news.ycombinator.com/item?id=2662694 [2] http://news.ycombinator.com/item?id=2698378

Re:Chrome 14 released by samstokes on Friday September 16, 2011 @02:02PM (#3005541)
It was covered as a future change, but as it breaks apps, it's important to note that this release brings it into the mainstream.
Re:Chrome 14 released by stanleydrew on Friday September 16, 2011 @02:08PM (#3005567)
Agreed, although you could argue that apps were already broken. Chrome just isn't as kind to broken apps anymore.