Bug 68337 – Images inside relatively-positioned links have incorrect offsetTop values

• Component: DOM
• Status: NEW

[Mark James]

The test URL has an image inside a link followed by a sized div inside a link. Each link is relatively positioned, and scripts are used to print the relative vertical position of each link with respect to its content block (image or div), via the content's offsetTop value.

Google Chrome Beta 14.0.835.163 (Webkit 91698, 07/25/2011) gives incorrect values of 0 for the first and 203 for the second (image attached). The value does not change if a vertical align setting changes the relative positions of the link and its content.

Firefox 6.0.1 gives the correct value of -37 for the first and an incorrect 0 for the second.

Internet Explorer 8 gives correct values of 2 and 21.

[Mark James]

Created attachment 107813 [details]
Rendering of test URL on Google Chrome Beta Version 14.0.835.163, September 14, 2011

[Mark James]

Note that a workaround for the image offset is

navigator.userAgent.indexOf('AppleWebKit/') >= 0 ?
 img.getBoundingClientRect().top-img.parentNode.getBoundingClientRect().top :
 img.offsetTop

[Ahmad Saleem]

Created attachment 461301 [details]
All browsers differ from each other

As can been seen from the attached screenshot, all browsers differ from each other based on test case attached in the URL field. Thanks!

[Ryosuke Niwa]

What a mess! Thanks for testing.

[alan]

This still runs legacy line layout. Will re-test it when IFC is enabled for positioned content.

[Ahmad Saleem]

@Alan - it seems that IFC fixed it but we have pixel difference - https://web.archive.org/web/20140806213230/http://advancedcontrols.com.au/w.html

Do we need to anything here?

[alan]

I'd be great if you could make a test reduction whenever you have some time.

[alan]

(In reply to alan from comment #7)
> I'd be great if you could make a test reduction whenever you have some time.
it would be great even :)