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

Issue 806689 link

Starred by 1 user
Status: Duplicate
Merged: issue 560809
Owner: ----
Closed: Feb 2018
Cc:
█ krajshree@chromium.org
█ mgiuca@chromium.org
dominickn@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Chrome - Custom external protocol doesn't open application

Reported by albertoh...@gmail.com, Jan 29 2018 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36

Steps to reproduce the problem:
1. We use links with a custom protocol to open a document and edit it with LibreOffice, 
2. Links are: sofficesigem://http://pathtodocument.odt

What is the expected behavior?
LibreOffice opens the document

What went wrong?
Since update to version 64 Chrome cuts the execution of LibreOffice

Did this work before? Yes 63

Does this work in other browsers? Yes

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

Comment 1 by krajshree@chromium.org, Jan 29 2018

Labels: Needs-Triage-M64 Needs-Bisect

Comment 2 by krajshree@chromium.org, Jan 30 2018

Cc: dominickn@chromium.org
Labels: Triaged-ET Needs-Feedback
ccing dominickn@ from issue https://bugs.chromium.org/p/chromium/issues/detail?id=788431 for further inputs on this issue.

albertohm76@ - Navigating to path http://pathtodocument.odt/ generates a site can't be reached error. Could you please provide any other sample url for further triaging of the issue from TE-end. 

Thanks...!!

Comment 3 by albertoh...@gmail.com, Jan 30 2018 

The documents are in a server that is only reachable form inside our organization and it is using WebDav.
 
The custom protocol 'sofficesigem' needs to be configured in Windows registry, we used this bat:

REG ADD HKEY_CLASSES_ROOT\sofficesigem /d "Url:sofficesigem Protocol"
REG ADD HKEY_CLASSES_ROOT\sofficesigem /v "URL Protocol"

REG ADD HKEY_CLASSES_ROOT\sofficesigem\DefaultIcon /d soffice.exe,1

REG ADD HKEY_CLASSES_ROOT\sofficesigem\shell
REG ADD HKEY_CLASSES_ROOT\sofficesigem\shell\open
REG ADD HKEY_CLASSES_ROOT\sofficesigem\shell\open\command /d "\"C:\Program Files (x86)\LibreOffice 5\program\soffice.exe\" %%1"

Anyway, we have managed to open the documents executing a bat that recreates the URL and launches LibreOffice. The last registry key now is:
HKEY_CLASSES_ROOT\sofficesigem\shell\open\command -> C:\Program Files (x86)\LibreOffice 5\program\lanzaOO.bat %1

So we have solved the problem that way.
Project Member

Comment 4 by sheriffbot@chromium.org, Jan 30 2018

Cc: krajshree@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "krajshree@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

Comment 5 by dominickn@chromium.org, Jan 30 2018

Cc: mgiuca@chromium.org
+mgiuca

Comment 6 by krajshree@chromium.org, Jan 31 2018

Labels: TE-NeedsTriageHelp
The issue seems to be out of TE-scope as it is related to configuring custom protocol 'sofficesigem' in Windows registry. Hence, adding TE-NeedsTriageHelp for further investigation from dev team.

Thanks...!!

Comment 7 by mgiuca@chromium.org, Feb 9 2018

Mergedinto: 560809
Status: Duplicate (was: Unconfirmed)
Looks like a dupe of  Issue 560809 .
►

Sign in to add a comment