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 Rendering | Assignee: | 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
Ojan Vafai
2009-04-21 16:06:21 PDT
Created attachment 29666 [details]
Simple testcase
(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. 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! |