If trimHttps is enabled, domain highlighting is not applied when loading suggested bookmark
Categories
(Firefox :: Address Bar, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox119 | --- | disabled |
firefox120 | --- | disabled |
firefox121 | --- | disabled |
firefox122 | --- | verified |
People
(Reporter: 6k64x4ma, Assigned: mseibert)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [sng-scrubbed][search-regression])
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:120.0) Gecko/20100101 Firefox/120.0
Steps to reproduce:
- Set
browser.urlbar.trimHttps
to true. - Open a new tab.
- Type something in the address bar and select suggested bookmark.
Actual results:
- The whole address is highlighted.
Expected results:
- Only the domain name should be highlighted.
Comment 1•1 year ago
|
||
:mseibert, since you are the author of the regressor, bug 1067293, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Issue is reproducible on:
- Firefox 119.0;
- Firefox 120.0b6;
- Nightly 121.0a1;
Tested and reproduced on:
- Windows 10;
- Ubuntu 22;
- macOS 12;
Setting as NEW so the developing team can have a look.
Updated•1 year ago
|
Corrected steps to reproduce:
- Set browser.urlbar.trimHttps to true.
- On any tab, type something in the address bar.
At this time, the auto-completed URL must be displayed. - Select suggested bookmark.
Updated•1 year ago
|
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 4•1 year ago
|
||
Depends on D192696
Assignee | ||
Comment 5•1 year ago
|
||
This is a result of two things:
- We don't format urls, when they don't start with a valid scheme (and slashes).
- We don't reformat, when
_urlMetaData
already contains the value of the urlbar.
For some reason the trimmed URL is placed in the meta data object. This in turn is compared to the trimmed value of the Urlbar. As a result no reformatting happens.
I created a patch that fixes the problem, but I can't write a test case as of now, because I don't know why it happens.
Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 6•1 year ago
|
||
Set release status flags based on info from the regressing bug 1067293
Updated•1 year ago
|
Comment 8•1 year ago
|
||
bugherder |
Updated•1 year ago
|
Reproducible on a 2023-11-03 Nightly build on macOS 12.
Verified as fixed on Firefox Nightly 122.0a1 on macOS 12, Windows 10, Ubuntu 22.
Description
•