New issue
Advanced search Search tips

Issue 890739 link

Starred by 2 users

Issue metadata

Status: Unconfirmed
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Documents don't open in Client Application when

Reported by dnilsso...@gmail.com, Oct 1

Issue description

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

Example URL:

Steps to reproduce the problem:
1. Open a SharePoint 2013 document library.
2. With the "Open documents in Client Application" featuer activated, click on the title of a document.
3. The document should open in the user's client application, but in our case it will open in the browser.

What is the expected behavior?
Open the document in the Client Application instead of OfficeWebApps (OWA) (on the browser).

What went wrong?
The document open on the browser with OWA instead of Client Applications.

Did this work before? Yes 

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

If we click on the Elipsis ("...") and then on "Edit", we can open the document in the client application. But the default behaviour of opening a document (when the "Open documents in client application" feature is activated) should be to open the documents in the client application when clicking on the title of the document. Not to open them in the browser with OWA.
This works as intended with InternetExplorer and Firefox, but not with Chrome...
 
Labels: Needs-Bisect Needs-Triage-M69
Components: -Internals>Network Internals>PlatformIntegration
I don't think this issue is related to Internals>Network. 
Tentatively changing label to Internals>PlatformIntegration.
Cc: phanindra.mandapaka@chromium.org
Labels: Triaged-ET TE-NeedsTriageHelp
dnilsson95@ Thanks for the issue...

As per comment #0, It seems to be related to SharePoint 2013 document library. Hence adding 'TE-NeedsTriageHelp' label to it and requesting the appropriate team to look into the issue and help in further triaging.

Thanks..!

Sign in to add a comment