New issue
Advanced search Search tips

Issue 749528 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

URL Shortcut Files Not Opening Correctly

Reported by ndel...@cedarburg.k12.wi.us, Jul 27 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Steps to reproduce the problem:
1. Domain joined machines with Win 7 and Win 10.
2. Chrome GPOs are shared and identical for Win 7 and 10 machines.
2. Win 7 machines with Chrome as default open URL files as expected.
3. Win 10 machines with Chrome as default open URL files as files.

What is the expected behavior?
Chrome should open the URL shortcut to a website.

What went wrong?
Chrome opens the URL file as a file. See attachment.

Did this work before? No 

Chrome version: 59.0.3071.115  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 26.0 r0
 
Capture.PNG
22.7 KB View Download
Cc: jsc...@chromium.org elawrence@chromium.org
Justin, Eric: Do we have a component for platform integration on Windows?
Components: Internals>PlatformIntegration
This sounds like  Issue 114871 .
Labels: Needs-Feedback
Bug Filer: Please open "Choose default apps by file type" in the system settings, scroll down to ".url file". Is "Internet Browser" is listed next to it?
Notably, this issue has 117 upvotes in the Windows 10 Insider's feedback hub since filing six months ago. Its status from Microsoft is set to "We've got it" although it's not clear what that means in this context.
The machine lists:

 .url
 Chrome HTML Document

and "Google Chrome" is shown as the default app.

URL files open as expected with Chrome if I change the default app from "Google Chrome" to "Internet Browser."

"Google Chrome" is no longer listed an option after changing it to "Internet Browser."

I set the default apps via a Windows 10 GPO, and this was needed in order to set Google Chrome as the default browser and avoid use prompts. We're a Google Apps school district, and so I didn't want IE or Edge to be the default browser. We have a shared folder on the network full or URL shortcuts that staff and students use.
Project Member

Comment 6 by sheriffbot@chromium.org, Jul 27 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "elawrence@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Correct, .URL should not be set to Chrome HTML Document.

I don't know much about the GPOs, but I think the problem is likely that the .URL registration is getting set to Chrome via GPO and should instead be left alone. The default "Internet Browser" handler is responsible for dispatching the URL open request to the system's default browser (Chrome, in your case).

Comment 8 by jsc...@chromium.org, Jul 27 2017

Cc: -jsc...@chromium.org georgesak@chromium.org
Components: Enterprise
Did your organization author its own Application Association XML file, or did you pull it down from somewhere else?

The XML for Chrome at https://support.google.com/chrome/a/answer/7009292?hl=en includes only HTTP, HTTPS, and .HTM
I authored the XML file from a configured reference machine.
Changed from:
 <Association Identifier=".url" ProgId="ChromeHTML" ApplicationName="Google Chrome" />
to:
 <Association Identifier=".url" ProgId="ChromeHTML" ApplicationName="Internet Browser" />
Thank you for your help.
I will follow up on any changes.
Status: WontFix (was: Unconfirmed)
Awesome, thanks for letting us know. And thanks Eric for jumping on this "bug" :)
Update:

The line below ended up fixing the issue. The default apps XML is applied at profile creation and so recreating Windows profiles was necessary to apply the new settings.

  <Association Identifier=".url" ProgId="InternetShortcut" ApplicationName="Internet Browser" />

Again, thank you for all the help!
Re #12: Thanks for confirming!

Sign in to add a comment