Open
Bug 1450435
Opened 6 years ago
Updated 2 years ago
Some URI components or Punycode domain names shouldn't have been decoded into Unicode, they should just be the original.
Categories
(DevTools :: Netmonitor, defect, P3)
Tracking
(Not tracked)
NEW
People
(Reporter: zjz, Unassigned)
Details
Attachments
(1 file)
5.91 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0 Build ID: 20180123231643 Steps to reproduce: This bug actually does the oppisite work of what bug 1448553 is going to do. bug 1448553 is going to decode those human-unreadable URLs or paths, which should have been decoded but are not decoded. On the contrary, there are cases where URI components or Punycode domain names should not have been decoded into Unicode but are decoded, so they should be restored to the original, for example, the request URL in the Headers panel of the Netmonitor should have displayed the raw header info, it doesn't make sense to display a modified one, even if it is readable than the raw one.
Reporter | ||
Comment 1•6 years ago
|
||
Updated•6 years ago
|
Component: Untriaged → Developer Tools: Netmonitor
Updated•6 years ago
|
Product: Firefox → DevTools
Comment 2•6 years ago
|
||
Sounds like you'd like to have a new UI (button, link, etc.) allowing the user to switch between original/decoded URLs? Any suggestions how the UI could look like? Honza
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(zjz)
Priority: -- → P3
Reporter | ||
Comment 3•6 years ago
|
||
I love the idea of having the choice of switching between original/decoded URLs, so that we don't miss the raw data while we are able to straightforwardly correspond the URLs.
Flags: needinfo?(zjz)
Reporter | ||
Comment 4•6 years ago
|
||
Currently, I don't have a strong opinion on how the UI should look like. But I am interested in it. Are there any folk who typically look into the UI issues?
Reporter | ||
Comment 5•6 years ago
|
||
I came up with a simple solution: Maybe we can list both the URLs, with the decoded one embraced by brackets([, ]), if the original URL is encoded?
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•