News for hackers. Stuff that matters.

A comment on Chrome team planning to block all access from browser to localhost wss. Parent comment

Re:Chrome team planning to block all access from browser to ... by kalleboo on Monday March 16, 2015 @06:48AM (#9210757)
> For example, it will break Dropbox's feature which allows you to open files from within the web app in a native application such as Excel (if you have the file synced on your computer).

Couldn't that just do that with a custom URL scheme like dropbox:// that's handled by the local app? Or is there more to the feature?

[ Parent | on HN ]
Re:Chrome team planning to block all access from browser to ... by Piskvorrr on Monday March 16, 2015 @06:57AM (#9210781)
The issue with custom URL schemes is that they're a cure worse than the disease here. The "internal webserver for local apps" was supposed to be a workaround for this very problem.
[ Parent | on HN ]
Re:Chrome team planning to block all access from browser to ... by jorangreef on Monday March 16, 2015 @07:22AM (#9210852)
Yes, the custom protocol scheme is also only really useful for doing something "once". That is, you can only issue one custom protocol request or so each time you load a web page, the browser blocks the rest to prevent spamming the user.
[ Parent | on HN ]