Closed Bug 232909 Opened 21 years ago Closed 20 years ago

css background image wrapping during text wrap

Categories

(Core :: Layout: Block and Inline, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: grenoml, Unassigned)

Details

User-Agent:       
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

When I declare a background image in a td and then the cell size is decreased
horizontally causing the text to wrap, the background image that was under the
text in its original position is still under the wrapped text.

Reproducible: Always
Steps to Reproduce:
1.create table td with background image
2.add length of text to cell
3.shrink browser so text in cell wraps

Actual Results:  
background image under the text in its original position stays behind text when
the text wraps.

Expected Results:  
the text should appear on top of whatever portion of the image that it has
wrapped over.
This occurs in Firebird 0.7.
The image was declared as repeat-x.  So the image actually would not tile
vertically.  I have the background color set to match the bottom of the image so
the text should actually be wrapping over the background color not the image.
How about a testcase? And also, please re-test with a current build.
.
Assignee: firefox → nobody
Component: General → Layout: Block and Inline
Product: Firefox → Browser
QA Contact: core.layout.block-and-inline
Version: unspecified → Trunk
I can't really figure out what you think should happen, but this seems to me to
be the desired behaviour.  Read bug 14777, which implemented the current
behaviour, and
http://www.hixie.ch/tests/adhoc/css/background/inline/policy/continuous/
http://www.hixie.ch/tests/adhoc/css/background/inline/policy/bounding-box/ and
http://www.hixie.ch/tests/adhoc/css/background/inline/policy/each-box/ for more.

So I think this is invalid, and I'm marking as such.  Re-open if you disagree
after reading the above material.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.