In the about:opentabs page the containers icons have no padding on the right side while hovered
Categories
(Firefox :: Tabbed Browser: Split View, defect, P3)
Tracking
()
People
(Reporter: atrif, Assigned: pranjalisrvgkp)
References
(Blocks 1 open bug)
Details
(Keywords: good-first-bug, Whiteboard: [fidefe-splitview][outreachy-sidebar-2026])
Attachments
(3 files, 3 obsolete files)
Found in
- 149.0a1 (2026-01-12)
Affected versions
- 149.0a1 (2025-01-12)
Tested platforms
- Affected platforms: Ubuntu 24, Windows 11, macOS 14
- Unaffected platforms: none
Steps to reproduce
- Add some tabs to a random container.
- Use the
Add Split Viewcontext menu option. - Inside about:opentabs hover over a tab that belongs to a container.
Expected result
- The container icon is correctly positioned inside the hover area.
Actual result
- The containers icons have no padding on the right side while hovered
Regression range
- Not a regression.
Additional notes
- Attached a screenshot.
Updated•3 months ago
|
Updated•3 months ago
|
Comment 1•2 months ago
|
||
To help Mozilla out with this bug, here's the steps:
- Comment here on the bug that you want to volunteer to help.
This will tell others that you're working on the next steps. - Download and build the Firefox source code
- If you have any problems, please ask on
Element/Matrix
in the#introductionchannel. They're there to help you get started. - You can also read the
Firefox Contributors' Quick Reference,
which has answers to most development questions.
- If you have any problems, please ask on
- Start working on this bug.
- If you have any problems with this bug,
please comment on this bug and set the needinfo flag for me.
Also, you can find me and my teammates on the#sidebarchannel on
Element/Matrix
most hours of most days.
- If you have any problems with this bug,
- Build your change with
mach buildand test your change with
mach test browser/components/tabbrowser/test/browser.
Also check your changes for adherence to our style guidelines by usingmach lint - Submit the patch (including an automated test, if applicable) for review.
Mark me as a reviewer so I'll get an email to come look at your code.- Getting your code reviewed
- This is when the bug will be assigned to you.
- After a series of reviews and changes to your patch,
I'll mark it for checkin or push it to autoland.
Your code will soon be shipping to Firefox users worldwide! - ...now you get to think about what kind of bug you'd like to work on next.
Let me know what you're interested in and I can help you find your next contribution.
| Assignee | ||
Comment 2•1 month ago
|
||
I would like to work on this if available
Comment 3•1 month ago
|
||
Thanks Pranjali! You may work on this bug.
Comment 4•1 month ago
|
||
Hi I will be happy to work on this
| Assignee | ||
Comment 6•1 month ago
|
||
I was assigned to work on this bug and I'm working on it.
Thanks everyone
Hi :nikkis, I'd like to volunteer to work on this bug.
I have reviewed the issue and noticed the container icon had inconsistent padding that caused misalignment within the hover area. I fixed this by applying margin-inline-end: 4px to .fxview-tab-row-container-indicator instead of padding, as margin adds spacing outside the element without
distorting the background image.
Patch submitted for review on Phabricator: https://phabricator.services.mozilla.com/D289089
Please see attached before/after screenshots for
visual comparison.
(In reply to Pranjali Srivastava from comment #6)
I was assigned to work on this bug, and I'm working on it.
Thanks everyone
Sorry about that, Pranjali—I didn’t notice this was already assigned.
I’ve already worked on a patch and submitted it for review. If it helps, you’re welcome to build on it or reuse anything from it. Otherwise, I’m happy to step back.
Thanks!
Updated•1 month ago
|
| Assignee | ||
Comment 10•1 month ago
|
||
For bug 2009917. Fix spacing issue in fxview tab row
Comment 11•1 month ago
|
||
Updated•1 month ago
|
Updated•1 month ago
|
Comment 12•1 month ago
|
||
:konyhéa, Pranjali already requested to work on this one. Sorry I missed that this morning when reviewing your patch. Can you please abandon any revisions you've created for this?
Updated•1 month ago
|
Comment 13•1 month ago
|
||
:kcochrane
Thanks for letting me know!
I’ll go ahead and abandon the revisions I created for this bug. I appreciate the clarification and look forward to contributing to other tasks.
Thanks again!
| Assignee | ||
Comment 14•1 month ago
|
||
Updated•1 month ago
|
Updated•1 month ago
|
Comment 15•1 month ago
|
||
Comment 16•1 month ago
|
||
| bugherder | ||
Comment 17•1 month ago
|
||
Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.
Comment 18•1 month ago
|
||
The patch landed in nightly and beta is affected.
:pranjalisrvgkp, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- See https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift for documentation on how to request an uplift.
- If no, please set
status-firefox150towontfix.
For more information, please visit BugBot documentation.
Updated•1 month ago
|
Updated•1 month ago
|
Updated•19 days ago
|
Updated•14 days ago
|
Updated•14 days ago
|
Description
•