Browser console - autocomplete menu truncated by window on resize
Categories
(DevTools :: Console, defect, P3)
Tracking
(firefox-esr68 wontfix, firefox74 wontfix, firefox75 wontfix, firefox76 fix-optional)
| Tracking | Status | |
|---|---|---|
| firefox-esr68 | --- | wontfix |
| firefox74 | --- | wontfix |
| firefox75 | --- | wontfix |
| firefox76 | --- | fix-optional |
People
(Reporter: cfogel, Unassigned)
Details
(Keywords: regression)
Attachments
(2 files)
Affected versions
- 75.0b5, 76.0a1 (2020-03-17)
Affected platforms
- Windows 10, macOS 10.15, Ubuntu 18.04;
Steps to reproduce
- Launch Firefox, enable DevTools, enable the pref: devtools.chrome.enabled
- Open the Browser Console;
- Shrink it to the minimum size;
- Type in anything in the input section to trigger the autocomplete menu;
- Resize the Browser Console window;
Expected result
- menu not clipped by size of window, as per the Console from DevTools;
Actual result
- menu not resized;
- might also worth checking if 1619876 can also be applied here (menu closed on resize)
Regression range
- will check if one and provide it asap;
Additional notes
- attached screenshot/recording with the issue;
Updated•1 year ago
|
Comment 1•1 year ago
|
||
Attaching the pushlog when the pop up is closed when resizing the browser console:
Last good revision: 679118259e91f40d4a8f968f03ec4cff066cdb5b (2016-07-10)
First bad revision: 214884d507ee369c1cf14edb26527c4f9a97bf48 (2016-07-11)
Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=679118259e91f40d4a8f968f03ec4cff066cdb5b&tochange=214884d507ee369c1cf14edb26527c4f9a97bf48
I think that this belongs to the Console component.
Nicolas, can you reproduce it?
Honza
Updated•1 year ago
|
Comment 3•1 year ago
|
||
yes, I can reproduce.
And this isn't console only, as I can also see it on the inspector; it's an issue in the autocomplete-popup component.
| Comment hidden (typo) |
Comment 5•1 year ago
|
||
oh sorry, I thought we were talking about a different issue, this is related to the console indeed
OK, good, thanks for the analysis Nicolas.
Honza
Comment 7•1 year ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)
Description
•