W3C home > Mailing lists > Public > public-css-archive@w3.org > August 2019

Re: [csswg-drafts] [cssom-view] [css-tables] should table.clientWidth include borders? (#4245)

From: François REMY via GitHub <sysbot+gh@w3.org>
Date: Tue, 27 Aug 2019 19:53:22 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-525456902-1566935601-sysbot+gh@w3.org>
I would tend to think that both client* and offset* properties should refer to the wrapper box, and that box doesn't have a border applied to itself, so it's clientTop should be 0 and its clientWidth should match its offsetWidth. From what you describe, this seems to match what Firefox is currently doing?

Besides, Chrome might need a fix regardless of the decision we take here, because clientTop currently ignores any space taken by the captions. I don't think it's reasonable for clientTop to not include the space taken by the captions if it is going to include the border of the table-grid box. I would rather keep math consistent.

Actually, this got me thinking: since the math in Chrome is not consistent, I suspected that the padding edge used for absolutely positioned elements would be incorrect in Chrome when a table was the containing block and it also had a caption, and it turns out it is indeed incorrect. 

https://wptest.center/#/sf7zh0 (click the "Refresh watches" button to see the values, seems like there is a race condition issue to be debugged here; then compare visually the position of the blue span in Chrome vs Edge/Firefox)

-- 
GitHub Notification of comment by FremyCompany
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4245#issuecomment-525456902 using your GitHub account
Received on Tuesday, 27 August 2019 19:53:24 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:52 UTC