I'm sure the "mc-auto-number-format" is the cause of the problem--the question is why is it there?
To explain, the kind of bulleted text in your example is normally coded as an unordered list (UL). If the same copy was numbered, it would be an ordered list (OL).
The CSS code you included (mc-auto-number-format: '{ }â— ';) looks to me like it was meant for an ordered list, since unordered lists don't need auto-numbering. If you open your topic in the Internal Text Editor, what code do you see?
Something like:
<ol>
<li>Text</li>
</ol>
OR:
<ul>
<li>Text</li>
</ul>
A more typical CSS entry for an unordered list with the round black bullet you want would be like this: ul
{
list-style-type: disc;
}
This CSS code would be rendered the same no matter what browser is used to view the output.
If you are using auto-numbering on a paragraph to give a list-like appearance, then it may depend on how you inserted that bullet icon. I usually use ALT and 0149 to insert a bullet icon. The appearance of that bullet icon differs between IE and Firefox (dark circle in IE and a diamond in FF). I've never seen it appear differently between flavors of IE. Is that the code you used to insert the bullet icon, or did you use a different sequence?
Lisa Eagles may soar, but weasels aren't sucked into jet engines. Warning! Loose nut behind the keyboard.
(Preface everything with "Importing from Frame, exporting to WebHelp")
I'm using auto-numbering on a paragraph to create nested lists.
<p class="Bullet_1"><i class="NewTerm">Objects </i>that are<i class="NewTerm"> <![CDATA[ ]]></i><MadCap:variable name="on-QStudioMPUserGuide.Product_on-Q" /> elements that you use to define the structure of your application.</p>
I will reinsert the bullet icon using your method. (I can't remember how I did it.)
Hi, Hanna. Bernie Meyer here (the tech writing contractor when you were hired at Ensequence). I saw your post about xrefs being duplicated in Flare, but then couldn't find it again! (So excuse me all, for posting off-topic.) Are you still having that problem, because I did, too, and it ended up being a bug in Flare. In my case it was because I embedded some font instructions in the FrameMaker xref definition. I had to remove them and impose them on the xref using the font catalog after creating the xref. That solved the problem double-xref output in Flare, but of course forces me to hand-apply font styling to my xrefs. Bleh. You can reach me directly at bernard.meyer@arrisi.com (I'm documenting TV software again). Hope all is well with you and the crew over there at Ensequence.