Ordered List in CASDM Knowledge document does not show in proper sequence in IE11. Works in Chrome.
The installation is R12.9 CP1 on a windows Server 2012 R2
Hello ashutosh2015 ,
How did you create the fancy schmancy "bullet list INSIDE a numbered list"?
Looking at Knowledge Documents "Edit Resolution" field there is only a "bullet list" OR a "numbered list" choice available that I can see.
So I suspect that you've used "Source" and done something that the Editor normally would not be able to do. Then IE throws a wobbly (technical term) when it encounters it.
Maybe have a look at a Source and see if you can get the code for that section rendered successfully on a different web page, as a suggestion.
Or just stick with the one list.
The built-in HTML editor in 12.9 can't easily create nested lists. You can still create them either by selecting Source and editing the HTML or by simply using a different editor. If you edit the source just make sure your tags are in the right order. If you are not familiar with HTML there are several good WYSIWYG editors that will produce clean HTML that you can just cut/paste into the Resolution section of your Knowledge Document. I recommend avoiding Microsoft products, such as Word since they create "ugly" HTML.
I created the following list by editing the source and it displays as expected in Chrome, IE10 and IE11.
Here is the source:
<p>List Example</p><br><br><ol><li>Item #1</li><li>Item #2</li><ul><li>Item 2.1</li><li>Item 2.2</li></ul><li>Item #3</li></ol><br>
Does this work out for you?
Thank you jmascaro and Kyle_R for your responses. I believe its likely an issue with dirty html code as pointed by jmascaro.
Although I still am inquisitive to know and learn how Chrome handles the same code better than IE 11.
With my Mod. hat on, I'm flagging jmascaro's post as the "Correct Answer" from the CA SDM side.
The question on why Chrome works better than IE in this instance is something more for Microsoft IE channel (Or Chrome as appropriate). If you wanted to, have a look at something like Fiddler or the IE/Chrome script debuggers against the page and see what the difference is. As jmascaro has demonstrated, some custom code will work fine across browsers.