Open Bug 1467714 Opened 6 years ago Updated 1 year ago

[Dev Tools] Flickering effect when resizing the Developer Tools window

Categories

(DevTools :: General, defect, P3)

61 Branch
Unspecified
macOS
defect

Tracking

(firefox60 affected, firefox61 affected, firefox62 affected)

Tracking Status
firefox60 --- affected
firefox61 --- affected
firefox62 --- affected

People

(Reporter: zstimi, Unassigned)

Details

[Affected versions]: 
- Firefox 61.0b11
- Firefox 60.0.2
- Firefox 62.0a1 (2018.06.06)

[Affected platforms]:
- Mac OS X 10.13

[Steps to reproduce]:

1. Open Firefox. Stay on Welcome page.
3. Open the Inspector by pressing F12. 
4. Click on the Meatball Menu then on settings menu item.
5. From Advanced settings section enable "Enable browser chrome and add-on debugging toolboxes" and "Enable remote debugging"
6. Go to Tools -> Web Developer -> Browser Toolbox to display the Developer Tools window.
7. Resize the Developer Tools window.

[Actual result]:
Flickering effect is displayed on Developer Tools window title menu.

[Expected result]:
The resize should be happened without any flickering effect.

[Regression range]:
- I will be back with regression range as soon as possible.

[Note]:
- This is happened only when in background of Developer Tools window is the Firefox welcome page.
This issue is reproduced only if in background of Developer Tools window is the Firefox welcome page since from Firefox 57(https://www.mozilla.org/en-US/firefox/57.0/firstrun/), if the welcome page is https://www.mozilla.org/en-US/firefox/56.0/firstrun/ or a smaller version of Firefox 56, the issue doesn't occur (the flicker not happens when resize the Developer Tools window).
Unfortunately, I couldn't found a regression range. Also, I want to mention that on Nightly (62.0a1) the issue is reproducible only on about:welcome page.
Product: Firefox → DevTools
Priority: -- → P3
Severity: normal → S3

I think we can remove the regressionwindow-wanted keyword per comment 1, and also given the fact the issue is 5 years old.

You need to log in before you can comment on or make changes to this bug.