Okay, some new observations: 1. I couldn't reproduce this on my laptop when it is disconnected from the docking station (hence disconnected also from the other 2 monitors). 2. Simply connecting or disconnecting the laptop from/to the docking station made this issue appear. To reduce variables here, I connected the DP straight to the laptop (without the docking station in the middle) and I could still reproduce this afterwards. 2a. When doing so, I noticed that the entire content area (or chrome UI? not sure) shifted down below the taskbar (this is also when the "flicker" occurs), and then back up to normal state (above the taskbar) a few moments after. A (more) reduced STR for me is: 1. Latest Nightly, Windows 10. (Not sure if required: use a somewhat slow PC) 2. Overflow the tab strip so that the All Tabs button would appear, and overflow the height of the screen when pressed 3. Click the All Tabs button -- the panel is overflowed, but the bottom part of the panel is visible -- all good so far 4. Connect/disconnect an external monitor -- this is when the taskbar "flicker" should occur 5. Click the All Tabs button -- the bottom part of the panel is beneath the taskbar, making the buttons/items there unclickable until you restart Nightly (In reply to :Gijs (he/him) from comment #2) > What causes the taskbar flicker? I think it's caused by connecting/disconnecting an external monitor. I assume that this happened to me initially because the monitors are disconnected when going to sleep, and upon waking up they are being reconnected.
Bug 1629479 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Okay, some new observations: 1. I couldn't reproduce this on my laptop when it is disconnected from the docking station (hence disconnected also from the other 2 monitors). 2. Simply connecting or disconnecting the laptop from/to the docking station made this issue appear. To reduce variables here, I connected the DP straight to the laptop (without the docking station in the middle) and I could still reproduce this afterwards. 2a. When doing so, I noticed that the entire content area (or possibly the chrome UI) shifted down below the taskbar (this is also when the "flicker" occurs), and then back up to normal state (above the taskbar) a few moments after. A (more) reduced STR for me is: 1. Latest Nightly, Windows 10. (Not sure if required: use a somewhat slow PC) 2. Overflow the tab strip so that the All Tabs button would appear, and overflow the height of the screen when pressed 3. Click the All Tabs button -- the panel is overflowed, but the bottom part of the panel is visible -- all good so far 4. Connect/disconnect an external monitor -- this is when the taskbar "flicker" should occur 5. Click the All Tabs button -- the bottom part of the panel is beneath the taskbar, making the buttons/items there unclickable until you restart Nightly (In reply to :Gijs (he/him) from comment #2) > What causes the taskbar flicker? I think it's caused by connecting/disconnecting an external monitor. I assume that this happened to me initially because the monitors are disconnected when going to sleep, and upon waking up they are being reconnected.
Okay, some new observations: 1. I couldn't reproduce this on my laptop when it is disconnected from the docking station (hence disconnected also from the other 2 monitors). 2. Simply connecting or disconnecting the laptop from/to the docking station made this issue appear. To reduce variables here, I connected the DP straight to the laptop (without the docking station in the middle) and I could still reproduce this afterwards. 2a. When doing so, I noticed that the entire content area (or possibly the chrome UI) shifted down below the taskbar (this is also when the "flicker" occurs), and then back up to normal state (above the taskbar) a few moments after. A (more) reduced STR for me is: 1. Latest Nightly, Windows 10. (Not sure if required: use a somewhat slow PC) 2. Overflow the tab strip so that the All Tabs button would appear, and overflow the height of the screen when pressed 3. Click the All Tabs button -- the panel is overflowed, but the bottom part of the panel is visible -- all good so far 4. Connect/disconnect an external monitor and wait for Windows to to its thing and sync everything up -- this is when the taskbar "flicker" should occur 5. Click the All Tabs button -- the bottom part of the panel is beneath the taskbar, making the buttons/items there unclickable until you restart Nightly (In reply to :Gijs (he/him) from comment #2) > What causes the taskbar flicker? I think it's caused by connecting/disconnecting an external monitor. I assume that this happened to me initially because the monitors are disconnected when going to sleep, and upon waking up they are being reconnected.
Okay, some new observations: 1. I couldn't reproduce this on my laptop when it is disconnected from the docking station (hence disconnected also from the other 2 monitors). 2. Simply connecting or disconnecting the laptop from/to the docking station made this issue appear. To reduce variables here, I connected the DP straight to the laptop (without the docking station in the middle) and I could still reproduce this afterwards. 2a. When doing so, I noticed that the entire content area (or possibly the chrome UI) shifted down below the taskbar (this is also when the "flicker" occurs), and then back up to normal state (above the taskbar) a few moments after. It seems that some of the Firefox components are not aware of the new height of the browser? A (more) reduced STR for me is: 1. Latest Nightly, Windows 10. (Not sure if required: use a somewhat slow PC) 2. Overflow the tab strip so that the All Tabs button would appear, and overflow the height of the screen when pressed 3. Click the All Tabs button -- the panel is overflowed, but the bottom part of the panel is visible -- all good so far 4. Connect/disconnect an external monitor and wait for Windows to to its thing and sync everything up -- this is when the taskbar "flicker" should occur 5. Click the All Tabs button -- the bottom part of the panel is beneath the taskbar, making the buttons/items there unclickable until you restart Nightly (In reply to :Gijs (he/him) from comment #2) > What causes the taskbar flicker? I think it's caused by connecting/disconnecting an external monitor. I assume that this happened to me initially because the monitors are disconnected when going to sleep, and upon waking up they are being reconnected.
Okay, some new observations: 1. I couldn't reproduce this on my laptop when it is disconnected from the docking station (hence disconnected also from the other 2 monitors). 2. Simply connecting or disconnecting the laptop from/to the docking station made this issue appear. To reduce variables here, I connected one of the monitors straight to the laptop (with the laptop disconnected from the docking station) and I could still reproduce this afterwards. 2a. When doing so, I noticed that the entire content area (or possibly the chrome UI) shifted down below the taskbar (this is also when the "flicker" occurs), and then back up to normal state (above the taskbar) a few moments after. It seems that some of the Firefox components are not aware of the new height of the browser? A (more) reduced STR for me is: 1. Latest Nightly, Windows 10. (Not sure if required: use a somewhat slow PC) 2. Overflow the tab strip so that the All Tabs button would appear, and overflow the height of the screen when pressed 3. Click the All Tabs button -- the panel is overflowed, but the bottom part of the panel is visible -- all good so far 4. Connect/disconnect an external monitor and wait for Windows to to its thing and sync everything up -- this is when the taskbar "flicker" should occur 5. Click the All Tabs button -- the bottom part of the panel is beneath the taskbar, making the buttons/items there unclickable until you restart Nightly (In reply to :Gijs (he/him) from comment #2) > What causes the taskbar flicker? I think it's caused by connecting/disconnecting an external monitor. I assume that this happened to me initially because the monitors are disconnected when going to sleep, and upon waking up they are being reconnected.