Can't change "Open with" binding for webloc files

OK, I realize this is a thread from stone age ... anyway, since I just had exactly the same problem, which had been driving me nuts for most of today now, I thought I might share my solution.

First things first:

* Nothing of what has been suggested here and what I've come across in various places all over the web actually worked.

* This issue is not confined to El Capitan. I'm on Sierra, and it exists there as well.

* It appears that the macOS doesn't honor the default app setting ("Open with") which can be set in a file's "Get info" dialog any more (it still did in Yosemite, afaik) -- .webloc files will always open in the system's default browser, regardless of the file's individual setting.

The solution is, to tell the web browser of choice explicitly to open the URL contained in a .webloc file. This can be done in various ways, I opted for AppleScript:

tell application "Safari"

activate

close every window

open location "https://icloud.com/"

end tell

Replace the argument to "tell application" with the browser of your choice, and the argument to "open location" with the URL contained in your .webloc file. Export as an app bundle, and maybe create an alias on your desktop (or wherever it's convenient for you).

Now you can just double-click the alias icon, and the URL will open in the designated browser.

Issue solved.

What happens if make the change in browsers preferences .

Firefox>Preferences>General

Safari webloc icons changed: Error code -10823

Please read this whole message before doing anything.

This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.

Step 1

The purpose of this step is to determine whether the problem is localized to your user account.

Enable guest logins* and log in as Guest. Don't use the Safari-only “Guest User” login created by “Find My Mac.”

While logged in as Guest, you won’t have access to any of your documents or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this behavior; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.

Test while logged in as Guest. Same problem?

After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.

*Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.

Step 2

The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.

Please take this step regardless of the results of Step 1.

Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem.

Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.

Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.

The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

Test while in safe mode. Same problem?

After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of Steps 1 and 2.