Last Comment Bug 590491 - Float content below body element pushes down background-position: bottom
: Float content below body element pushes down background-position: bottom
Status: RESOLVED DUPLICATE of bug 333382
:
Product: Core
Classification: Components
Component: Layout: Floats (show other bugs)
: Trunk
: x86 All
: -- normal (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
Mentors:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-08-25 06:09 PDT by Sander
Modified: 2015-08-06 22:00 PDT (History)
6 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments
testcase (751 bytes, text/html)
2010-08-25 06:09 PDT, Sander
no flags Details

Description Sander 2010-08-25 06:09:55 PDT
Created attachment 469029 [details]
testcase

See the attached testcase. Chrome and Opera have the background image (the orange bar) bottom positioned to the regular block, while Gecko has it start at the bottom of the floating block, which sticks outside the body element. (Gecko's behaviour is more desired, imo, but Opera and webkit are correct according to the spec, as far as I understand it. This is dangerous with people mostly just testing in Firefox.)

Tested in gecko 2.0b3 20100805.
Comment 1 David Baron :dbaron: ⌚️UTC+2 (mostly busy through August 4; review requests must explain patch) 2010-08-25 08:47:39 PDT
I guess the question here is something that's actually a little ambiguous in the spec:  whether the "root" block formatting context is established by the root element or by something above the root element.  If it's established by the root element, then the root should use the height rules in 10.6.7 and this is correct.  But I can't tell from 9.4.1 what establishes the root BFC.
Comment 2 David Baron :dbaron: ⌚️UTC+2 (mostly busy through August 4; review requests must explain patch) 2010-08-26 09:01:14 PDT
Posted http://lists.w3.org/Archives/Public/www-style/2010Aug/0539.html
Comment 3 David Baron :dbaron: ⌚️UTC+2 (mostly busy through August 4; review requests must explain patch) 2012-02-08 00:47:46 PST
The CSS WG discussed this at today's meeting (and at the end of yesterday's) and concluded Gecko is wrong.
Comment 4 Sander 2012-02-08 01:34:34 PST
FWIW, webkit seems to have since changed its behaviour, and is now doing the same as Gecko. (Since at least Chromium 14.)
Comment 5 philippe (part-time) 2012-02-08 04:14:54 PST
(In reply to Sander from comment #4)
> FWIW, webkit seems to have since changed its behaviour, and is now doing the
> same as Gecko. (Since at least Chromium 14.)

Indeed, Safari 5.1.3 (534.53.10) and WebKit latest nightly (r107048) running on OS X 10.7.3 show the same behaviour as Gecko.
Comment 6 David Baron :dbaron: ⌚️UTC+2 (mostly busy through August 4; review requests must explain patch) 2015-08-06 22:00:25 PDT

*** This bug has been marked as a duplicate of bug 333382 ***

Note You need to log in before you can comment on or make changes to this bug.