New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 753766 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

Application Link Handlers not launching applications on Windows 10

Reported by frhem...@gmail.com, Aug 9 2017

Issue description

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

Steps to reproduce the problem:
1. Open chrome
2. Open OneDrive Office365 from within Chrome
3. Open a Word/Excel file that is shared there
4. CHoose Edit in Excel or Word
5. Nothing happens

It works when you download the file first and the re-upload it. It also still works in IE11.

What is the expected behavior?
The Chrome browser should launch the rich client (Office365 client) and load the document there.

What went wrong?
Chrome doesn't do anything

Did this work before? Yes 59

Chrome version: 60.0.3112.90  Channel: stable
OS Version: 10.0
Flash Version: 

This was an earlier ticket: https://bugs.chromium.org/p/chromium/issues/detail?id=378822
 

Comment 1 by hdodda@chromium.org, Aug 10 2017

Cc: hdodda@chromium.org
Labels: Needs-Feedback
Tested the issue on windows 10 using chrome M60 #60.0.3112.90 and followed steps below:

1. launched chrome and opened OneDrive Office365within chrome.
2. opened excel file that is in onedrive and choosed edit with excel.
3. And file opened to edit.

Attached screenshot for reference.

@frhemrev-- Could you please check attached screenshot and confirm us if we have missed any steps and please help us by providing the expected result screenshot.

Thanks!
753766.PNG
72.9 KB View Download

Comment 2 by ajha@chromium.org, Oct 11 2017

Labels: -Needs-Feedback
Status: WontFix (was: Unconfirmed)
Closing the issue as there is no user update on this for long. Feel free to file a new issue or ping this bug if you still encounter this or any other issue on Chrome.

Thank you!

Sign in to add a comment