Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

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

This thread was archived. Please ask a new question if you need help.

Jerky scrolling with pictures when in full screen mode

  • 2 majibu
  • 2 wana tatizo hili
  • 24 views
  • Last reply by jesduo

jesduo
jesduo
more options

Reproducing the problem in both Firefox and Firefox Beta:

  • enable full screen
  • view an image
  • pinch to zoom in to make the image a bit larger than the screen vertically (for example 50% larger)
  • slowly scroll up and down, and see the image move irregularly in a jerky way when the address bar is close to fully visible

Any way to disable this annoying behaviour?

Btw: This is the easiest way to show the problem, but it will also occur in certain web pages.

Reproducing the problem in both Firefox and Firefox Beta: * enable full screen * view an image * pinch to zoom in to make the image a bit larger than the screen vertically (for example 50% larger) * slowly scroll up and down, and see the image move irregularly in a jerky way when the address bar is close to fully visible Any way to disable this annoying behaviour? Btw: This is the easiest way to show the problem, but it will also occur in certain web pages.

All Replies (2)

crankygoat
crankygoat
more options

Yeah i can duplicate that on most attempts. That is some strange drawing behavior. Seems more a bug than something adjustable.

jesduo
jesduo Mwenye swali
more options

FYI: I reported this issue in bugzilla https://bugzilla.mozilla.org/show_bug.cgi?id=1514553. However, it is marked as a duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=1277712. Sadly, it seems fixing this problem is not prioritized, so I urge everyone affected to upvote it, so maybe it will eventually be fixed.