110.0.1 misplaced icons in toolbars with no "Bookmark toolbar items"
Categories
(Firefox :: Toolbars and Customization, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox110 | --- | wontfix |
firefox111 | --- | verified |
firefox112 | --- | verified |
People
(Reporter: 08xjcec48, Assigned: emilio)
References
(Regression)
Details
(Keywords: regression)
Attachments
(2 files)
Steps to reproduce:
Users who had removed the Bookmark toolbar items
element from their toolbars are reporting that their custom icons are misplaced after updating to Firefox 110.0.1:
https://old.reddit.com/r/firefox/comments/11evixz
https://old.reddit.com/r/firefox/comments/11fgnlc
https://old.reddit.com/r/firefox/comments/11g98xd
Comment 1•2 years ago
|
||
This appears to have been caused by changing a rule from width: 0;
(which overrides the natural width of the text content of the element) to min-width: 0;
for #personal-toolbar-empty-description
in bug 1812636:
<hbox id="personal-toolbar-empty" skipintoolbarset="true" removable="false" nowidth="">
<description id="personal-toolbar-empty-description" data-l10n-id="bookmarks-toolbar-empty-message"
onclick="BookmarkingUI.openLibraryIfLinkClicked(event);"
onkeydown="BookmarkingUI.openLibraryIfLinkClicked(event);">
For quick access, place your bookmarks here on the bookmarks toolbar.
<html:a xmlns:html="http://www.w3.org/1999/xhtml" data-l10n-name="manage-bookmarks"
class="text-link" tabindex="0">Manage bookmarks…</html:a>
</description>
</hbox>
https://searchfox.org/mozilla-release/source/browser/themes/shared/browser-shared.css#222 et seq.
#PersonalToolbar[collapsed=false] > #personal-toolbar-empty[nowidth] > #personal-toolbar-empty-description {
margin-inline: 0;
min-width: 0; /*** previously this was width: 0; ***/
white-space: nowrap;
position: relative;
z-index: 1;
}
Updated•2 years ago
|
This can be seen also during Firefox's startup, even if there are bookmarks there.
Comment 3•2 years ago
|
||
:emilio, since you are the author of the regressor, bug 1812636, could you take a look? Also, could you set the severity field?
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Comment 4•2 years ago
|
||
The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.
Assignee | ||
Comment 5•2 years ago
|
||
I'm confused, I can't repro this on a clean profile? What are the conditions on which this happens?
Comment 6•2 years ago
|
||
(In reply to Emilio Cobos Álvarez (:emilio) from comment #5)
I'm confused, I can't repro this on a clean profile? What are the conditions on which this happens?
STR that work for me:
- new profile
- open customize mode
- remove import button + bookmarks toolbar items from the toolbar
- put any other toolbar button there by dragging it from the palette
- exit customize mode
- open new window (or restart Firefox, presumably)
Does that help?
Assignee | ||
Comment 7•2 years ago
|
||
Ah yeah, I guess I missed (6). Thanks!
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 8•2 years ago
|
||
Updated•2 years ago
|
Assignee | ||
Comment 10•2 years ago
|
||
It's probably worth backing out the offending patch from beta/next dot release.
Comment 12•2 years ago
|
||
(In reply to Emilio Cobos Álvarez (:emilio) from comment #10)
It's probably worth backing out the offending patch from beta/next dot release.
I only have the end user perspective, but wouldn't it be simpler to add back this width
rule that was changed to a min-width
rule?
#PersonalToolbar[collapsed=false] > #personal-toolbar-empty[nowidth] > #personal-toolbar-empty-description {
width: 0;
}
Assignee | ||
Comment 13•2 years ago
|
||
Well that's effectively what backing out would do right?
Comment 14•2 years ago
|
||
(In reply to Emilio Cobos Álvarez (:emilio) from comment #13)
Well that's effectively what backing out would do right?
You're right. I thought there were other changes, but it's just a comment.
Comment 15•2 years ago
|
||
bugherder |
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 16•2 years ago
|
||
Comment 17•2 years ago
|
||
A patch has been attached on this bug, which was already closed. Filing a separate bug will ensure better tracking. If this was not by mistake and further action is needed, please alert the appropriate party. (Or: if the patch doesn't change behavior -- e.g. landing a test case, or fixing a typo -- then feel free to disregard this message)
Comment 18•2 years ago
|
||
Setting 111 to Fixed, Bug 1812636 was backed out of beta
Comment 19•2 years ago
|
||
Comment 20•2 years ago
|
||
bugherder |
Comment 21•2 years ago
|
||
This issue is verified as fixed in our latest Nightly build 112.0a1 (2023-03-12) as well as our latest RC 111.0 .
Description
•