When switching from non-retina to retina, rendered HTML is offset

UNCONFIRMED
Unassigned

Status

()

UNCONFIRMED
4 years ago
3 years ago

People

(Reporter: sean, Unassigned, NeedInfo)

Tracking

36 Branch
x86
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: gfx-noted)

(Reporter)

Description

4 years ago
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:36.0) Gecko/20100101 Firefox/36.0
Build ID: 20150219174507

Steps to reproduce:

On my Macbook pro, I had an external monitor plugged in (dual screen set up). My Firefox window was on the non-retina external monitor's desktop. Then I unplugged my monitor. This put the Firefox window on my only desktop, which is now retina.

I'm currently on FF 36.0 (I believe I'm in the beta channel, still). This was also happening in the 36 betas.


Actual results:

The rendered HTML is offset on the left, as seen in this screen shot:
https://www.dropbox.com/s/r2e99ccq8z6vhjg/Screenshot%202015-02-27%2008.49.06.png?dl=0

I'm not sure this happens *every* time, but it happens enough to be annoying (read: it's not a one-off).

The example shows only an offset on the left, but I believe I've also seen dead space offsets like this on the top, bottom, and right.


Expected results:

After reloading the page, Firefox displays it as this:
https://www.dropbox.com/s/z9bdbpcfsr0yuk9/Screenshot%202015-02-27%2008.53.08.png?dl=0

It should never have rendered with the offset.

Updated

4 years ago
Component: Untriaged → Graphics
Product: Firefox → Core
Maybe :mattwoodrow?
Flags: needinfo?(matt.woodrow)
Whiteboard: gfx-noted
(Reporter)

Comment 2

4 years ago
FWIW, I thought this might have been fixed in `37.0` (which I am currently on), but it happened again today.
Version: 36 Branch → 37 Branch
(Reporter)

Comment 3

3 years ago
Again, I was hopeful that this was fixed, but this morning (on 41.0b8) it happened again: https://www.dropbox.com/s/8xvngzcvb521nia/Screenshot%202015-09-11%2010.05.56.png?dl=0 (VirtualBox bug not related (-: )
(Reporter)

Updated

3 years ago
Version: 37 Branch → 41 Branch
(Reporter)

Comment 4

3 years ago
Not sure if it's useful for me to keep updating this way, but it happened again just now on 42.0b3.
This time it was when switching from retina to non-retina. It may have been this way all along, actually, now that I think of it.
Version: 41 Branch → 42 Branch
It's good to know that the bug hasn't mysteriously disappeared however the version field should reflect the original version of the bug. That said this has been awaiting attention for several months. Milan, who is the right person to look into this?
Flags: needinfo?(milan)
Version: 42 Branch → 36 Branch
Yes, this has been around forever and there are a few different bugs on the subject.  External monitors and different screen resolution multipliers confuse things.
Flags: needinfo?(milan)
(Reporter)

Comment 7

3 years ago
Still happening on 43. This time when switching from non-retina external monitor to built-in retina.
(In reply to Sean Coates from comment #7)
> Still happening on 43. This time when switching from non-retina external
> monitor to built-in retina.

Hi Sean, I don't think you need to keep updating here to say it's still happening. It's safe to say the issue will persist as long as we're not actively working to fix it. That said, it might be good to know if it mysteriously disappears at some point.

Milan, what do you need to move this forward?
(Reporter)

Comment 9

3 years ago
OK. Cool. I certainly don't want to be annoying about it; was just updating major versions, but I don't need to.

It'll be hard to tell if it does mysteriously disappear because it rarely happens.

Let me know if you need any additional info that you think I might have.
You need to log in before you can comment on or make changes to this bug.