Bug 25314

Summary: In quirks mode, body.clientHeight > body.offsetHeight when you put padding on the HTML element
Product: WebKit Reporter: Ojan Vafai <ojan>
Component: Layout and RenderingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: ahmad.saleem792, apavlov, bfulgham, dtrebbien, erik.arvidsson, gur.trio, hyatt, priyajeet.hora, rniwa
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Mac   
OS: OS X 10.5   
Attachments:
Description Flags
Simple testcase none

Ojan Vafai
Reported 2009-04-21 16:06:21 PDT
Summary: In quirks mode, body.clientHeight > body.offsetHeight when you put padding on the HTML element It's not clear to me what the right thing to do here (whether they should be equal or have offsetHeight>clientHeight), but it's clear that the current behavior is wrong.
Attachments
Simple testcase (1005 bytes, text/html)
2009-04-21 16:07 PDT, Ojan Vafai 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Ojan Vafai
Comment 1 2009-04-21 16:07:39 PDT
Created attachment 29666 [details] Simple testcase
gur.trio
Comment 2 2013-09-11 00:13:12 PDT
(In reply to comment #0) > Summary: In quirks mode, body.clientHeight > body.offsetHeight when you put padding on the HTML element > > It's not clear to me what the right thing to do here (whether they should be equal or have offsetHeight>clientHeight), but it's clear that the current behavior is wrong. behaviour seems correct http://dev.w3.org/csswg/cssom-view/#dom-htmlelement-offsetheight http://dev.w3.org/csswg/cssom-view/#dom-element-clientheight ClientHeight : viewport height Offsetheight : renderer's height.
Ahmad Saleem
Comment 3 2022-07-26 14:12:55 PDT
In all browsers (Chrome Canary 106, Firefox Nightly 104 and Safari 15.6 on macOS 12.5), body.clientHeight is great than body.offsetHeight using attached test case. I am not clear on web-spec or expected behaviour but since all browsers are aligned, I think we can mark this as "RESOLVED CONFIGURATION CHANGED" or "RESOLVED WONTFIX". Thanks!
Note You need to log in before you can comment on or make changes to this bug.