I brought up our quick look test case for lists and the nested list markers are not displaying correctly. For example, I expected to see an unordered list display like this: disc square circle disc square circle in NGLayout it is displayed like this: disc circle square square square square

Running the test in navigator, I see disc, circle, square, square, square... which is what nglayout does.

The display in Nav is being changed in 5.0 to display correctly. In the current release, it is displayed incorrectly. The way I have described it above is the way it is suppose to be displayed

Actually, there is no way it is "supposed" to be displayed according to the specs. Currently, NGLayout's behavior is: 1. Consistent with HTML and CSS specifications 2. Consistent with Navigator 4.x behavior Since those are our design goals in this area, this bug is invalid. Note content developers are free to control the type of bullet rendered using CSS. They can set it to be disc, square, etc., or even to a specific image URI.

you have missed the point Angus, what if I don't use CSS, what if I have an older document, how will the nested markers be displayed -- that is the point. In the 4.0 spec the type attribute is deprecated, however, we still need to account for default values if and when a CSS script is not present. If you look at the 3.2 spec, the attribute values for the type attribute are clearly defined and in the order that is expected. I have as yet not seen a plan on what the default markers will be and how we will handle nested lists when a CSS script is not present. Reopening bug.

There is no language whatsoever that I can find in the HTML4 DTD that indicates the user agent should render lists as you indicate. The closest language I can find is in section 10.3.1 which is "normative" information, not mandatory for spec compliance: For the UL element, possible values for the type attribute are disc, square, and circle. The default value depends on the level of nesting of the current list. These values are case-insensitive.

marking bug as verified, using CSS to set the style is the most approrpiate approach.