Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Wo archive tread sia. Meɖekuku bia biabia yeye ne ehia kpeɖeŋu.

Why is screen positioning erratic in fullscreen mode?

  • 2 ŋuɖoɖowo
  • 1 masɔmasɔ sia le esi
  • 18 views
  • Nuɖoɖo mlɔetɔ chuckbaldwin

chuckbaldwin
chuckbaldwin
more options

After upgrading from v3.x.x to v.4.0.1, Firefox doesn't start Maximized like the desktop shortcut says. Instead it starts with the Title Bar separated from the rest of the window, and won't allow me to Maximize without leaving fullscreen (FS) mode.

After leaving FS mode, Maximizing, and re-entering FS mode, the inital window is OK. But subsequently, opening new tabs, or swithching between tabs, often causes erroneous positioning. Leaving & re-entering FS mode (i.e. pressing F11 twice) corrects the condition. This behaviour didn't occur in v3.x.x.

After upgrading from v3.x.x to v.4.0.1, Firefox doesn't start Maximized like the desktop shortcut says. Instead it starts with the Title Bar separated from the rest of the window, and won't allow me to Maximize without leaving fullscreen (FS) mode. After leaving FS mode, Maximizing, and re-entering FS mode, the inital window is OK. But subsequently, opening new tabs, or swithching between tabs, often causes erroneous positioning. Leaving & re-entering FS mode (i.e. pressing F11 twice) corrects the condition. This behaviour didn't occur in v3.x.x.

All Replies (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Try to disable hardware acceleration.

  • Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"

If disabling hardware acceleration works then check if there is an update available for your graphics display driver.

chuckbaldwin
chuckbaldwin Biabia la
more options

Disabling hardware acceleration had no effect. I just installed FF 5.0, and the same problem continues to occur. I'm surprised nobody else has seen this. Am i the only one that uses fullscreen?