Created attachment 8508284 [details] Screen Shot 2014-10-20 at 3.11.59 PM.png After moving my Fx window from my bigger screen to the smaller screen an resizing the Fx window to the smaller screen, the Hello drop down window seems to stay in the proportions of the big screen. See attached screen shot.
Sorry this was on Nightly 36.0a1 (2014-10-20)
status-firefox36: --- → affected
Created attachment 8508288 [details] Screen Shot 2014-10-20 at 3.23.48 PM.png This is how it looks in proper proportions after restarting Nightly.
Is there any way to recover from this state? Does this affect Firefox 34 or 35?
iirc this is an issue with retina to non-retina displays, and Social API suffers the same issue.
Summary: Loop drop down window does not rescale after rescaling Fx → Loop drop down window does not rescale after rescaling Fx (retina to non-retina)
is this an issue that social API is planning to address (and if so has anyone done the research). sounds like we are seeing a sizing issues similar to what Social API sees.
backlog: --- → Fx38?
(In reply to sescalante from comment #5) > is this an issue that social API is planning to address (and if so has > anyone done the research). sounds like we are seeing a sizing issues > similar to what Social API sees. Anything that has a panel with iframe/html is going to suffer this issue, it's not a SocialAPI thing. No, I am not planning on taking this on. Someone who understands retina issues and can actually test this would be better at figuring it out.
This is looking very much like bug 803383
Since bug 803383 is resolved, we should confirm if this is still a problem.
Priority: -- → P5
Whiteboard: [triage] → [reconfirm]
The main issue I get now is when moving from retina to non-retina, I get three-quarters of the panel as "black", with only a quarter showing the panel. The resolution does appear to be right though...
Nils, Mark: is this still a problem in the latest Nightly? It sounds like it could be the same as bug 1249279, which should now be fixed.
Yeah I think it was probably fixed by that bug, maybe a couple of others as well.
Just tested it again: still broken in 47, but fixed in 48.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla48
OK.... what's the build date of your FF47 where it's still broken? (The fix in bug 1249279 landed on aurora late on 2016-04-11; I'm not sure if an update has gone out yet.)
Sorry just updated my FF47. But I had last updated my FF47 some time last week. So it was definitely before 2016-04-11.
You need to log in before you can comment on or make changes to this bug.