bugzilla.mozilla.org will be intermittently unavailable on Saturday, March 24th, from 16:00 until 20:00 UTC.

CSS-defined bullets (<LI>) don't appear upon first loading




18 years ago
17 years ago


(Reporter: Blake Ross, Assigned: Kevin McCluskey (gone))



Windows 98

Firefox Tracking Flags

(Not tracked)


(Whiteboard: [nsbeta2+][6/15][FIX], URL)


(1 attachment)



18 years ago
Build ID: 2000042008

Load Moz and visit the URL above.  Scroll down to where it says "Sluzba (WWW i 
WAP) bezi na vsech adresach: " in the right column of the large table.  Below 
it is an HTML list (using <UL> to start it and <LI> for the bullets).  The same 
type of bulleted lists appear in two gray and yellow columns near the bottom of 
the page.  Near the top of the page in the source is CSS defining the image to 
be used for the bullets (it's a sideways red triange).  However, upon first 
loading the website, I am unable to see these image bullets.  Instead, I see a 
normal list with no bullet/image next to it (which would be the typical result 
if the browser couldn't load the image or the image didn't exist in the 
specified path).  However, if you (or I, at least) reload the page, these 
bullets then show up.

What's going on here?

Comment 1

18 years ago
The list element should reflow when the image is received. I'm going to attach a 
better testcase. Instead of reloading the page, just resize it to cause a reflow 
of the list. Reassigned to HTML Element.
Assignee: pierre → rickg
Component: Style System → HTML Element
QA Contact: chrisd → petersen

Comment 2

18 years ago
Created attachment 8385 [details]

Comment 3

18 years ago
Definitely a layout bug.
Assignee: rickg → buster

Comment 4

18 years ago
Waqar:  here's a interesting image-related bug.  I'll bet what's happening here 
is the bullet frame isn't properly dealing with the incremental reflow that is 
issued when the image loads the first time.   The second time through, the image 
is in the cache and we get the data back for it immediately, so it works fine.

We need to fix this for proper CSS1 compliance.
Assignee: buster → waqar
Keywords: css1
Priority: P3 → P2
nsbeta2 6/1-.
Keywords: nsbeta2

Comment 6

18 years ago
Taking this bug from Waqar
Assignee: waqar → kmcclusk


18 years ago

Comment 7

18 years ago
Putting on [nsbeta2+][6/15] radar.
Whiteboard: [nsbeta2+][6/15]
*** Bug 41169 has been marked as a duplicate of this bug. ***
The bug I just marked as a duplicate seems to be the same basic problem,
although perhaps with slightly different symptoms.  In that bug (see simple
testcase attached to it), the images are aligned incorrectly the first time they
load, since (I presume) the dimensions are not known at initial reflow, and the
incremental reflow doesn't reflow the list items.

Comment 10

18 years ago
Setting Milestone to M17
Target Milestone: --- → M17

Comment 11

18 years ago
I have a fix for this in my tree. The problem was the bullet frame was not 
asked to reflow after the image came in because it does not live within a 
line. The solution was to mark the line dirty instead of the bullet frame 
when the image comes in. 

        // The bullet frame is not in a line list so marking it dirty
        // has no effect. The reflowing of the bullet frame is done 
        // indirectly.
Whiteboard: [nsbeta2+][6/15] → [nsbeta2+][6/15][FIX]

Comment 12

18 years ago
Changed nsBulletFrame to set the dirty flag on it's parent's first frame instead 
of on itself when it's image is updated. 

Setting the dirty flag on the BulletFrame does not work because the BulletFrame 
is reflowed only when the line which contains
the <LI>'s  text is reflowed. The BulletFrame itself does not reside inside a 
line, so it was not being reflowed when the <LI>'s
image eventually loaded. 

Fixed in 6/8/2000 4:35PM build
Last Resolved: 18 years ago
Resolution: --- → FIXED
*** Bug 42177 has been marked as a duplicate of this bug. ***

Comment 14

18 years ago
Fixed in the June 19th build (2000061908).
SPAM. HTML Element component deprecated, changing component to Layout. See bug
88132 for details.
Component: HTML Element → Layout
You need to log in before you can comment on or make changes to this bug.