Closed
Bug 1642076
Opened 4 years ago
Closed 4 years ago
Unwanted vertical scrollbars in Cookies panel
Categories
(DevTools :: Netmonitor, defect, P2)
DevTools
Netmonitor
Tracking
(firefox79 verified)
VERIFIED
FIXED
Firefox 79
Tracking | Status | |
---|---|---|
firefox79 | --- | verified |
People
(Reporter: Honza, Assigned: lelouch.cpp)
References
(Blocks 2 open bugs)
Details
Attachments
(2 files)
STR:
- Open DevTools and select the Network panel
- Load google.com
- Select the first request and go to the Cookies panel
- See Response and Request cookies sections, they show vertical scrollbars => BUG
ER: The vertical scrollbars should not be there
Honza
Reporter | ||
Updated•4 years ago
|
Blocks: netmonitor-cookies-sidepanel, 1403203
I would like to take this issue if some isn't working on it already.
Thank you.
Comment 2•4 years ago
|
||
@kriyszig Assigned to you! Thanks for looking at this.
Assignee: nobody → lelouch.cpp
The table element used to view the acodion is responsible for
introducing the scroll bar as per the browser toolkit.
Adding a 3px bottom padding to the tbody element solves the issue
caused by table row's padding going beyound the computed height.
Reporter | ||
Updated•4 years ago
|
Summary: Unwanted vertical scrollbars → Unwanted vertical scrollbars in Cookies panel
Updated•4 years ago
|
Attachment #9153016 -
Attachment description: Bug 1642076 - Remove unwanted scrollbar in the Network Details' Cookie panel r=Honza,bomsy → Bug 1642076 - Add test to prevent unwanted scrollbar in the Network Details' Cookie panel r=Honza,bomsy
Pushed by jodvarko@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/676e1c3e21e6
Add test to prevent unwanted scrollbar in the Network Details' Cookie panel r=Honza,bomsy
Comment 5•4 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox79:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 79
Comment 6•4 years ago
|
||
Fix verified with 79.0b2 on macOS 10.15.5, Windows 10, Ubuntu 18.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•