trouble using custom scheme uri in multiple iframe
Reported by
xqv...@gmail.com,
Jun 24 2016
|
|||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36 Example URL: https://jsfiddle.net/xqvier/Lv6pedqL/4/ Steps to reproduce the problem: 1. create a webpage using 2 iframes 2. point these iframes with the src attribute to a custom scheme URI (ie. ms-word:http//.../) What is the expected behavior? When using an http URI scheme, the browser offer to download multiple files the first time, then automatically download all the files on next visits (see : https://jsfiddle.net/Lv6pedqL/1/) When using custom URI scheme, it should open both of them. What went wrong? only the first iframe is managed (the document open itself in word.) (see : https://jsfiddle.net/xqvier/Lv6pedqL/4/) Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? N/A Chrome version: 51.0.2704.103 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 22.0 r0 You will need Microsoft word to test thoses 2 fiddles
,
Jul 4 2016
Hello, Can you provide any news regardingng this issue ? (won't fix / work as intended / will look into it ?) I'm looking forward to this because i don't have any knowledge of the application source and i'd rather have someone knowing what he is doing than trying to look for myself and pushing an incorrect resolution (ftr, my knowledge on this code language is really poor). Thank you for your concern
,
Jul 29 2016
xqvier, do you mean you registered ms-word: protocol by registerProtocolHandler() [1] or OS's protocol handler setting? [1] https://html.spec.whatwg.org/multipage/webappapis.html#custom-handlers
,
Aug 4 2016
Hi, No, i didn't register the protocol handler via the webpage. Microsoft Office register itself (at system level I think) to handle ms-word protocol during installation. (https://msdn.microsoft.com/en-us/library/office/dn906146.aspx ยง1.4)
,
Aug 5 2016
,
Aug 5 2016
cannot reproduce because: $ wget https://srv.xqvier.com/webdav/Test-document-1.docx --2016-08-05 16:23:35-- https://srv.xqvier.com/webdav/Test-document-1.docx Resolving srv.xqvier.com (srv.xqvier.com)... 37.59.39.38 Connecting to srv.xqvier.com (srv.xqvier.com)|37.59.39.38|:443... failed: Connection refused. Thoughts: * People watching Blink>Loader are generally notvery knowledgeable in custom schemes (inculding me), tkent: there should be a better label? * Added a few folks to CC in case they know where to route this * DoS-wise, not sure we want to make it possible for a webpage to spam a user with numerous msword: windows, leaning towards working as intended (added mkwst@ who is orders of magnitude more knowledgeable here)
,
Aug 5 2016
Sorry, I had to put the http server down for work-related purpose. I'll turn it back on Sunday. Will keep you tuned. Regarding the "work as intended" suggestion. Isn't it possible to make it work like the multiple download behavior ? Meaning : prompting the user with an alert that the webpage is trying to open multiple application related links ? Regards
,
Aug 10 2016
HTTP server back online. You should be able to reproduce now. Sorry for the delay.
,
Aug 12 2016
Loading triager here. Changing component to downloads as it seems more related.
,
Jan 10 2017
Moving out of downloads, since that part is working as intended. It seems like the the issue is with the URL not being handled by the correct plugin.
,
Apr 12 2017
,
Apr 12 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 13 2018
Still p3 |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by pdr@chromium.org
, Jun 24 2016Components: -Blink Blink>HTML>CustomHandlers