Closed Bug 194831 Opened 22 years ago Closed 7 years ago

unpopulated/empty <LI> is not rendered unless redrawn (doctype dependent)

Categories

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

x86
All
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mrmazda, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug, )

Details

(Keywords: testcase)

Attachments

(4 files)

trunks Above URL has four unpopulated <LI> tags. 2003022408 Linux and 2003022412 OS/2 display them as bullets beside whitespace, just like IE6. Win 2003022408 renders as if they didn't exist.
Working with Moz 1.3b on WinXP. If I have my window at full-screen (1024x768), I see the bug. If I shrink it down, I do see the empty <LI>'s.
The size does not matter. What matters is that a reflow will make them show up (eg open/close the sidebar). But initially they are hidden. Felix, could you possibly create a minimal testcase? (remove all HTML not needed to reproduce the bug).
Strict behaves different than the others, not depending on a window resize., but always doing it wrong
All my tests done at 1024x768. No difference if charset statement is omitted from head. Amplifying summary to include doctype and redraw. On further study, this is not OS dependent. The original URL (4.01 loose) behaves differently than the testcases. Fullscreen, the empties are not displayed until redraw. Windowed, the empties are always displayed. I think the difference is that the original doesn't fit entirely in the viewport regardless like the testcases do. Except for top margin difference, the 4.01 loose and 3.2 testcases behave the same. Regardless whether opened fullscreen or windowed, the empties are omitted until redraw. 4.01 strict doesn't care about redraw. It always displays a siamese. I suppose maybe this should be a separate bug.
Keywords: testcase
OS: Windows 98 → All
Summary: unpopulated/empty <LI> is not rendered → unpopulated/empty <LI> is not rendered unless redrawn (doctype dependent)
Looks like a inline box model thing; the Strict testcase especially is weird-looking.
Assignee: other → block-and-inline
Component: Layout → Layout: Block & Inline
This is at least partly caused by the incorrect fix for bug 75963 (which should have been fixed by associating the bullet with a different frame). Making pfd->GetFlag(PFD_ISBULLET) (in addition to the current text frame condition) force zeroEffectiveSpanBox to false helps a little, though.
*** Bug 226880 has been marked as a duplicate of this bug. ***
Confirming HTML 4.01 strict testcase shows overlapping bullets HTML 4.01 loose and HTML 3.2 testcases only show 3 items, each with a bullet. Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7a) Gecko/20040113 Firebird/0.8.0+
Depends on: 54979
Is this the same bug as bug 383289? If yes, we can dupe bug 383289 to this one.
Assignee: layout.block-and-inline → nobody
QA Contact: ian → layout.block-and-inline
Decreasing the priority as no update for the last 2 years on this bug. See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage about the priority meaning.
Priority: P1 → P5
The testcases all work now.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: