Page 1 of 1

2.5.6rc1 regression: placeholder positioning/spacing

Posted: Thu Sep 27, 2012 12:10 am
by al_9x
Fx 16.0b5, NS 2.5.6rc1+, new profile, block iframes on trusted

compare https://login.live.com/login.srf?id=2 between 2.5.5 and 2.5.6rc1

Re: 2.5.6rc1 regression: placeholder positioning/spacing

Posted: Thu Sep 27, 2012 10:07 am
by Giorgio Maone
Fixed in latest development build 2.5.7rc2, thanks.

Re: 2.5.6rc1 regression: placeholder positioning/spacing

Posted: Thu Sep 27, 2012 2:45 pm
by therube
Just to note, the build is there, just not reflected on the webpage, https://secure.informaction.com/downloa ... 5.7rc2.xpi.

Re: 2.5.6rc1 regression: placeholder positioning/spacing

Posted: Thu Sep 27, 2012 3:39 pm
by Giorgio Maone
therube wrote:Just to note, the build is there, just not reflected on the webpage, https://secure.informaction.com/downloa ... 5.7rc2.xpi.
Fixed, thanks.

Re: 2.5.6rc1 regression: placeholder positioning/spacing

Posted: Fri Sep 28, 2012 4:10 am
by al_9x
a related regression that's not resolved by 2.5.7.rc2:

compare a google translated iframe (activated and loaded)

Re: 2.5.6rc1 regression: placeholder positioning/spacing

Posted: Mon Oct 01, 2012 11:50 am
by Giorgio Maone
Fixed in latest development build 2.5.7rc3, thanks.

Re: 2.5.6rc1 regression: placeholder positioning/spacing

Posted: Thu Oct 04, 2012 5:40 am
by al_9x
Giorgio Maone wrote:Fixed in latest development build 2.5.7rc3, thanks.
another regression, in google image search results (click on an image from the results list/table) the image used to be on top of the placeholder, now it's below, obscured by it.

The zorder change may be intentional but in this case the old way was definitely better. Can it be made smarter or optional?

Re: 2.5.6rc1 regression: placeholder positioning/spacing

Posted: Fri Oct 05, 2012 12:03 am
by GµårÐïåñ
Not always, so it would be a pretty ugly hack.

Re: 2.5.6rc1 regression: placeholder positioning/spacing

Posted: Fri Oct 05, 2012 1:46 pm
by Giorgio Maone
al_9x wrote: The zorder change may be intentional but in this case the old way was definitely better.
In this case maybe, but definitely not.
The change (relocating the placeholder on top if its central part is obscured by something else) has been made because Youtube started placing its custom placeholders for HTML 5 videos over the video element, and therefore of the placeholder, obscuring it completely.
While you can easily remove the placeholder (shift+click) and anyway see through it if it's on top, if it's on bottom you're just left with broken content and no obvious way to unlock it (until you look at the Blocked Objects submenu, but it's not obvious for most people).