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

Firefox UI not updating on change

  • 1 reply
  • 1 has this problem
  • 8 views
  • Last reply by twolfson

more options

After updating to Firefox 46, my URL bar started being placed in the wrong position. This wasn't a major issue but more recently I shifted from 2 monitors to 1 monitor (also upgraded to 46.0.1) and the UI started not updating when the website changed (e.g. I scroll or type and the UI doesn't properly display changes until I mouse over the area or change window focus).

I have tried Safe Mode and disabling hardware acceeleration but neither seem to resolve the issue.

The issue appears inconsistently (e.g. it shows up on first scroll but not afterwards) but occurs more frequently the longer Firefox runs.

I have recorded a GIF via FFmpeg of what I am encountering. This was in a Safe Mode run. It's too big for Mozilla's uploader so I have posted it to imgur:

http://i.imgur.com/ZvRgknw.gifv

OS information: Linux Mint 17.1 with Cinnamon desktop environment

After updating to Firefox 46, my URL bar started being placed in the wrong position. This wasn't a major issue but more recently I shifted from 2 monitors to 1 monitor (also upgraded to 46.0.1) and the UI started not updating when the website changed (e.g. I scroll or type and the UI doesn't properly display changes until I mouse over the area or change window focus). I have tried Safe Mode and disabling hardware acceeleration but neither seem to resolve the issue. The issue appears inconsistently (e.g. it shows up on first scroll but not afterwards) but occurs more frequently the longer Firefox runs. I have recorded a GIF via FFmpeg of what I am encountering. This was in a Safe Mode run. It's too big for Mozilla's uploader so I have posted it to imgur: http://i.imgur.com/ZvRgknw.gifv OS information: Linux Mint 17.1 with Cinnamon desktop environment

Modified by twolfson

All Replies (1)

more options

I worked around the issue by sticking with Firefox@45 until the recent Firefox@48 release which seems to have resolved the issue.