Opened 16 years ago
Closed 15 years ago
#2117 closed defect (fixed)
table sizing broken
Reported by: | bill | Owned by: | sjmiles |
---|---|---|---|
Priority: | high | Milestone: | 0.9 |
Component: | HTML | Version: | 0.4.1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
http://archive.dojotoolkit.org/nightly/tests/style/test_sizing.html reports incorrect results about tables on IE:
DEBUG: ---mytable--- DEBUG: outer size: actual=[90, 41], expected=[110, 60, ] DEBUG: inner size: actual=[80, 31], expected=[100, 50, ] DEBUG: content size: actual=[60, 11], expected=[80, 30, ]
... and also on FF:
DEBUG: ---mytable--- DEBUG: outer size: actual=[114, 64], expected=[110, 60, ] DEBUG: inner size: actual=[114, 64], expected=[100, 50, ] DEBUG: content size: actual=[108, 58], expected=[80, 30, ]
Also I wonder if the test itself is invalid, because width/height have different meanings depending on the browser. (border box sizing vs. content box sizing)
Change History (5)
comment:1 Changed 15 years ago by
Milestone: | → 0.9 |
---|---|
Owner: | changed from psowden to Tom Trenka |
comment:2 Changed 15 years ago by
Component: | String → HTML |
---|
comment:3 Changed 15 years ago by
Hmm, I'm not sure. The consensus is that we want to continue supporting getMarginBox() and getContentBox()... but setMarginBox() on a table... I thought browsers didn't support setting the size of a table.
comment:4 Changed 15 years ago by
Owner: | changed from Tom Trenka to sjmiles |
---|
Possibly fixed with r8943. Reassigning to Scott, just in case.
comment:5 Changed 15 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Mostly the ...box functions should now work with TABLE and BUTTON, which generally have border-box model.
However, <table> should be given margin: 0 for maximum compatibility with ...box functions. See #3296.
Bill, Should I keep this open, given all the discussions around measurements we've had in the past 2 weeks?