Closed Bug 261522 Opened 21 years ago Closed 21 years ago

Only partial rendering of background of nested div

Categories

(Core :: Layout, defect)

x86
Windows ME
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: wimroffel, Assigned: MatsPalmgren_bugz)

References

()

Details

(Keywords: testcase)

Attachments

(2 files)

User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98; Win 9x 4.90; T312461; WMM) Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.7.3) Gecko/20040910 First of all: see the code of the example page: it is only 33 lines. And the page also contains an image how it looks on my pc. I have a menu system where menu's consist of anchors inside a div: <div class="menu"> <a href="periods.htm">Periods 2</a> <a href="instruments.htm">Instruments 2</a> </div> When I put a second menu div inside the first I get the display problem. From the nested menu only the left side of the background is displayed. Reproducible: Always Steps to Reproduce: 1. See above 2. 3.
Probably a duplicate of bug 170927.
Attached file Example file
The link was to the example was/is in the URL field (http://www.classiccat.net/text9.html), but I think the attachment is a more appropriate place.
I seems as if this is not just rendering. Mousehandling is different too. In the new example file I have added onmouseover and onmouseout messages. If you test this under Mozilla you will just get messages when you come over a link and when you leave it again. If you test the same in IE you get much more messages: one for entering and leaving the padding, one for coming over the link and leaving it again, one for coming over the margin between the two links, etc. The conclusion: the area is not just not colored with the backgroundcolor, it also ísn't considered part of the DIV as far as the mouse concerns. The small colored zone at the left IS mousesensitive.
WORKAROUND: For my own site I have implemented as a workaround "style='width:120'" or the dynamic variant "menudiv.style.width=". It takes some calculation to get the right width (getting the offsetwidth of all the anchor elements and adding a margin) but then it is not difficult. That leaves the question why it is so difficult to solve this bug in Mozilla.
Not a GFX issue, and almost certainly a duplicate of bug 201897.
Assignee: win32 → nobody
Component: GFX: Win32 → Layout
Depends on: 201897
QA Contact: ian → core.layout
Keywords: testcase
One additional comment: Normally the outermost DIV displays OK and the second and lower levels give problems. However, if you set the width of the first level explicit, the second level will be OK too and the problems start at the third level. Similary setting the second level will make the third level OK. So my theory would be that somehow the sourcecode is looking at the higher level for the width there and getting problems if it doesn't find it.
Assignee: nobody → mats.palmgren
The layout problem should have been fixed by bug 201897, please reopen if not. If there was a mouse event bug also, then please file a separate bug on that. -> FIXED (by bug 201897)
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: