- From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Jan 2022 06:50:36 +0000
- To: public-css-archive@w3.org
> @dholbert Sorry my original description was not clear. > https://github.com/web-platform-tests/wpt/blob/master/css/CSS2/normal-flow/block-in-inline-client-rects-001.html includes 3 test cases, each for `getBoundingClientRect` and `offsetWidth`. The bullet item is about `t1.getBoundingClientRect` test case results 200 for Blink/Gecko while 500 for WebKit. Gotcha - so WebKit differs from Blink/Gecko on the **getBoundingClient** behavior for this scenario with an empty descendant. But all three are in agreement on how offsetWidth behaves (and in Gecko/Chromium, it behaves consistently between offsetWidth and getBoundingClient). Here's the live WPT test, FWIW: Results: https://wpt.fyi/results/css/CSS2/normal-flow/block-in-inline-client-rects-001.html Live test: https://wpt.live/css/CSS2/normal-flow/block-in-inline-client-rects-001.html > I didn't find specific mention about the item 2 (when width or height is zero) in the IRC log I'm not sure it was discussed; in my [question above](https://github.com/w3c/csswg-drafts/issues/6588#issuecomment-1006201558), I was trying to interpret the resolution, which just says to include the dimensions of the box, and doesn't have "unless it's zero height" exclusion. But, yeah -- I think the point of the resolution was to **clarify how offsetWidth/offsetHeight behave** -- not to change getBoundingClientRect. So: given that the WebKit-specific behavior here is specific to getBoundingClientRect and disagrees with the existing & uncontroversial (I think?) spec text for that feature (which is not the feature we were intending to modify here), I think it's safe to say we did *not* resolve on matching that WebKit-specific behavior. i.e. I think the answer to my "....and maybe also this:" above is "no, not also that." @chrishtr if you could confirm that we're on the same page, that would be helpful - thanks! -- GitHub Notification of comment by dholbert Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6588#issuecomment-1010695486 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 12 January 2022 06:50:38 UTC