Bug 28810 – offsetWidth of elements containing nested in block level elements reported as 0

• Component: Layout and Rendering
• Status: NEW

[Daniel Wagner-Hall]

Created attachment 38734 [details]
Page showing bug

The offsetWidth of elements containing block-level elements is incorrectly reported as 0, rather than the maximum offsetWidth of any of its sub-elements.

Note that IE and Firefox return different values for offsetWidth due to bounding box differences, but both behave as above for the nested case.

[Carl Hempel]

I'm also experiencing this bug

[Marek Stepien]

I can also see this bug in Safari 5 and recent Chrome 6 dev builds.

[Greg Dennis]

I see this in Chrome 5 and Chrome 6 beta.

[Niall Smart]

Reproduced in Chrome 11.0.696.68

[paynalton]

Confirmed on Chromium 14.0.835.163 and Safari 5.0 (7533.16).

Problem extended to multiple IMG elements into a div and another div with css

IMG:
 width:auto;
 height:100%;

Containerdiv:
 width:noSet;
 height:noSet;

ContainerContainerDiv:
 width:300px;
 height:300px;


Structure:

Div class ContainerContainerDiv
  Div class ContainerDiv
    IMG
    IMG
    IMG

javascript:

alert(IMG_DOM_ELEMENT.offsetWidth)  //Result: 0

[Ahmad Saleem]

I am able to reproduce this bug using attached test case in Safari 15.6 on macOS 12.5 and it shows "test2.offsetWidth: 0" - which is what this bug about. Here are results from other browsers:

** Firefox Nightly 105 **

test1.offsetWidth: 96
test2.offsetWidth: 1277

** Chrome Canary 106 **

test1.offsetWidth: 96
test2.offsetWidth: 1287 (There was another bug where Chrome was different from Firefox with just 10 px and it was about scrollbar - just want to add some note here)

** Safari 15.6 on macOS 12.5 **

test1.offsetWidth: 96
test2.offsetWidth: 0

Just find updated results. Thanks!

[Radar WebKit Bug Importer]

<rdar://problem/97694011>