Case of URI fragment after hash mark cannot be edited in search bar
Categories
(Firefox :: Address Bar, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox86 | --- | wontfix |
firefox87 | --- | wontfix |
firefox88 | --- | verified |
People
(Reporter: fabrizio, Assigned: daisuke)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:85.0) Gecko/20100101 Firefox/85.0
Steps to reproduce:
- Go to invalid URL https://docs.docker.com/engine/reference/builder/#COPY
- Edit the URL in search bar to correct the case of the fragment "COPY" to the correct one, "copy" (in lowercase) and press enter
Actual results:
Firefox insists on invalid upper case #COPY and it is impossible to manually correct the uri
Expected results:
I should be allowed to modify the case of the url fragment
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Address Bar' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Comment 2•3 years ago
|
||
Thanks for filing this.
We correctly preserve the case in the input, but when you hit enter, we take the URL from the heuristic, which has the original case (and that's incorrect in this scenario).
Daisuke, are you interested in taking this? No problem if not, or if you're busy.
Assignee | ||
Comment 3•3 years ago
|
||
Thank you very much for pinging me, Drew.
Yep, I will take a look at this issue.
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 4•3 years ago
|
||
Comment 5•3 years ago
|
||
A non-obvious workaround is to paste the correct URL and hit enter. I'm not saying that's the final outcome of this bug, just noting it.
Updated•3 years ago
|
Updated•3 years ago
|
Pushed by dakatsuka.birchill@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/02385a038230 Avoid autofilling if uri fragment does not match with case-sensitive. r=adw
Comment 7•3 years ago
|
||
bugherder |
Comment 8•3 years ago
|
||
Hi,
I've verified that this bug has been fixed on Nightly 88.0a1 (2021-03-16) on windows 10.
Regards, Flor
Description
•