Custom protocol URL is built incorrectly
Reported by
natalie....@gmail.com,
Oct 28 2016
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/53.0.2785.143 Chrome/53.0.2785.143 Safari/537.36 Steps to reproduce the problem: 1. Go to http://example.com/ 2. Open Console, register a protocol handler: navigator.registerProtocolHandler("web+grr", "http://example.com/%s?%s", "NB: two %s"); and click "Allow". 3. Enter "web+grr:substitute" in the address bar. What is the expected behavior? Browser should load http://example.com/web%2Bgrr%3Asubstitute?%s replacing only the first %s in the template with the encoded URL. What went wrong? Browser loads http://example.com/web%2Bgrr%3Asubstitute?web%2Bgrr%3Asubstitute replacing all %s in the template. Did this work before? N/A Does this work in other browsers? Yes Chrome version: 53.0.2785.143 Channel: stable OS Version: Flash Version: "When the user agent uses this handler, it must replace the *first* occurrence of the exact literal string "%s" in the url argument..." https://html.spec.whatwg.org/multipage/webappapis.html#dom-navigator-registerprotocolhandler
,
Dec 29 2016
Please find the attached screencast for reference.
,
Dec 29 2016
,
Jan 9 2017
,
Jan 19 2017
Thanks for the report.
,
Aug 22 2017
Bulk disowning per sshruthi's email about bug triage best practices.
,
Aug 22
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
,
Aug 23
It seems this works correctly with Chrome 69 Beta. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by jmukthavaram@chromium.org
, Dec 29 2016Labels: Needs-Feedback