Open
Bug 1449939
Opened 8 years ago
Updated 1 year ago
Should we EncodeURIComponent the tags in place:tag queries? (tags containing an ampersand are broken)
Categories
(Toolkit :: Places, defect, P2)
Toolkit
Places
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox62 | --- | fix-optional |
| firefox63 | --- | affected |
People
(Reporter: mak, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [sng-scrubbed])
Currently we just put the tag in there, that means we could end up generating invalid uris in some case. When we work on the new API, we want to do something about it.
|
Reporter | |
Updated•8 years ago
|
Summary: Should we EncodeURIComponent the tags in place:tag queries? → Should we EncodeURIComponent the tags in place:tag queries? (tags containing an ampersand are broken)
|
||
Updated•8 years ago
|
status-firefox62:
--- → fix-optional
status-firefox63:
--- → affected
|
||
Updated•3 years ago
|
Severity: normal → S3
|
||
Comment 4•3 years ago
|
||
The severity field for this bug is relatively low, S3. However, the bug has 3 duplicates.
:mak, could you consider increasing the bug severity?
For more information, please visit auto_nag documentation.
Flags: needinfo?(mak)
|
||
Comment 5•3 years ago
|
||
The last needinfo from me was triggered in error by recent activity on the bug. I'm clearing the needinfo since this is a very old bug and I don't know if it's still relevant.
Flags: needinfo?(mak)
|
||
Comment 6•3 years ago
|
||
If we encode the component part of the URL, this should work. Then we'll need to decode when showing the URL in the UI.
Whiteboard: [fxsearch] → [sng-scrubbed]
|
||
Updated•3 years ago
|
See Also: → https://mozilla-hub.atlassian.net/browse/SNG-754
You need to log in
before you can comment on or make changes to this bug.
Description
•