1. Create a new page in SS 2.7f.
2. Set page to center horizontally.
3. Create a text object and enter multiple lines.
4. Set the text to justify fully.
5. Set the same text to a bulleted list.
6. Preview the page, and check the result in FF.
7. In my FF, the text attributes in 4 and 5 above cause the objects above the text object to "lean" or "hang" to the left of the page.
If I remove the text formatting, the problem goes away.
8. My system: XP Pro, FF with NoScript.

This problem had me completely baffled for 30 minutes, I'm pushing to meet a deadline for a client site.

I copied the text object to a new page, and previewed with the same result.

Anyone able to duplicate this, or did I mess something up?

I haven't tried to duplicate it yet. As you're in a hurry, for now I'll just say that bullets have caused problems in the past -- check this thread.

plaZma,

Did you look at the HTML that SS is publishing? I tried your test steps and did not see a problem. I then added an extra bullet (also justified), with no problem. I then added a new line between the rwo bullets, and made the new line a non-bullet. Bingo, your error appeared.

When I did this, the HTML was:

 <div id="Oobj2"
 style="position:absolute;z-index:1;visibility:visible;
 left:40px;top:35px;width:129px;height:207px;">
<div id="Grtf2" class="dfltt">
<ul>

[*]<div align="justify">
<font face="Verdana" color="#000000">Now is the time fr all good men to come to the aid of their country.
</ul>
</div><div align="left"><ul>
[*]
</div
<div align="justify">The quick brown fox jumped over the lazy dog's back.</ul><br></font>
</div>
</div>
</div>
 

As you can see, the order of div and ul tags are incorrect. The div for the blank line contains the start ul/li tag for the second bullet. When the div tag is closed, so is the list, which leaves the text justified but not part of a bullet.

Hi guys,
Larry is right, there is the origin of this problem.
So best to avoid that combination of items, or to manually fix it in code view.

So is this a bug or not?

Yes it's a bug. We shouldn't be able to do things on the workpage that cause incorrect code.

I have also been able to duplicate a problem quite similar to the one you described. And, if I remember correctly, if you play fast and loose with font changes or bolding in bulleted lists, that also can cause incorrect tag ordering.

We're aware of this one and it is on our list.