Issue 654963 link

Starred by 1 user

Issue metadata

Status:	ExternalDependency
Owner:	----
Cc:	█ a.obzhirov@samsung.com rbasuvula@chromium.org style-bugs@google.com
Components:	Blink>CSS
EstimatedDays:	----
NextAction:	----
OS:	Linux , Windows , Mac
Pri:	2
Type:	Bug
M-55 Via-Wizard Hotlist-Interop

Chrome should honor "the HTML body element" in `offsetTop`

Reported by dewqa...@gmail.com, Oct 12 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36

Steps to reproduce the problem:
https://github.com/w3c/csswg-drafts/issues/584

What is the expected behavior?

What went wrong?
Does not follow the spec

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 53.0.2785.143  Channel: stable
OS Version: OS X 10.12.0
Flash Version: Shockwave Flash 23.0 r0

Comment 1 by sebastia...@gmail.com, Oct 12 2016

The point of this issue is to only return 0 for the first <body> element child of the root <html> element, but handle subsequent <body> elements like normal elements.[1][2]
I.e. when calling 'offsetTop' and 'offsetLeft' on *descendant* <body> elements, you should get their offsets returned instead of 0.

I've attached the test case of the GitHub issue.

Sebastian

PS: The same issue was filed for Gecko.[3]

[1] https://drafts.csswg.org/cssom-view/#dom-htmlelement-offsettop
[2] https://drafts.csswg.org/cssom-view/#the-html-body-element
[3] https://bugzil.la/1309427

test case.html
256 bytes View Download

Comment 2 by rbasuvula@chromium.org, Oct 12 2016

Cc: rbasuvula@chromium.org
Labels: M-55 OS-Linux OS-Windows
Status: Untriaged (was: Unconfirmed)

Tested the issue on Chrome Stable #53.0.2785.143, Canary 56.0.2888.0 on Mac OS X 10.12 ,Ubuntu 14.04 & Win 10.0 and was able to reproduce the issue.

This is a Non-Regression issue seen from M30# 30.0.1549.0 (208818), marking the status to Untriaged so that the issue would get addressed.

Thank You.