Link for custom protocol with json not longer recognized
Categories
(Core :: Networking, defect)
Tracking
()
People
(Reporter: aurelius.slawinski, Unassigned)
References
(Regression)
Details
(Keywords: regression)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0
Steps to reproduce:
When using a custom protocol, a link with json structure is not recognized anymore:
<a href="vscode://{'cmd':'openFile'}">link not ok</a>
However, a workaround to get this to work again is using a slash like this:
<a href="vscode:///{'cmd':'openFile'}">link workaround</a>
I am using vscode protocol here just as an example:
See https://jsfiddle.net/aLvg0dn3/2/
Actual results:
The link is not clickable (does not appear in the left lower corner as link).
Expected results:
Link should be clickable as usual. In chrome, the link still works.
Updated•8 months ago
|
Updated•8 months ago
|
Comment 1•8 months ago
|
||
:edgul, since you are the author of the regressor, bug 1603699, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Comment 2•8 months ago
|
||
The correct way to represent such URLs is:
<a href="vscode:{'cmd':'openFile'}">link ok</a>
This will get fixed by bug 1877753 in the next Firefox dot release next week.
Description
•