411387 - Padding around templated listitems increases when items are containers

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Iain Coghill]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11

When an RDF:Seq is referenced in a template for a listbox widget, and the child items in that container are also containers, there is extra padding around the items displayed. 

Further, when an item is selected, the padding increases again for each selection.

Reproducible: Always

Steps to Reproduce:
1.Create .rdf file with a top-level RDF:Seq whose children are also RDF:Seq containers.
2.Create .xul window with a templated listbox which references top-level container and listitems labels are constructed from child containers.
3.Repeatedly select items in list.
Actual Results:  
Padding above and below items in list is initially greater than normal.
As each item is selected the padding for all items grows further.

Expected Results:  
Padding should be the same regardless of whether the items are containers or not. Padding should not increase as items are selected.

Comment 1

[Tyler Downer [He/Him]]

This bug was originally reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.6 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode

Comment 2

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.8 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.