Fixed issues
These issues are fixed in Dynamic Documentation for the Tridion Docs 15.1 release.
Search
A search through content in a language other than the default language no longer produces results with titles only in the default language. Now the result titles are in the language of the searched content.
Images and multi-media
- Embedded videos were not appearing and could not be played.
- Images with a fixed size did not render properly and arge images could not be viewed in their actual size.
Sometimes images need to maintain a fixed size, such as imagemaps that have clickable areas defined and these need to remain aligned with the image. You can give an image a fixed size within a topic by setting the height and width properties. DITA provides a
scalefitattribute, which achieves a fixed-size image when set to "no", but Dynamic Documentation ignored the attribute. Dynamic Documentation now maintains the height and width properties set for images, and it also provides scroll bars if the image is too big for the content pane.
Table of Contents and navigation issues
- The tree showed topic navtitles rather than the topic Title elements, as it should.
- Hovering over a tree node title or bookmark item should display a tooltip with the start of the topic’s short description, but it did not.
- The panel did not properly word wrap words long titles, and was not resizable.
- Topic header titles in the sidebar are broken mid-word.
- A conref in a topic title did not appear in the TOC or breadcrumb.
- Tree panel would jump if you select a topic that occurs multiple times in the tree.
- Topic switcher dropdown appeared even if there was only a single item and it was not needed.
- Topic switcher dropdown does not take you to the same topic.
Topic formatting
- Some DITA elements were not rendering properly. The following problems in rendering have now been fixed with changes to the CSS for the Dynamic Documentation:
- The
apinameelement should be rendered in a monospace font, but was not. - The
cmdnameelement should rendered be in a monospace font, but was not. - The
filepathelement should rendered be in monospace bold, but was rendered in plain monospace. - The
optionelement should rendered be in monospace font, but was not. - The
parmnameelement should be in monospace font, but was instead rendered in bold. - Headers of a table should be rendered in mixed case, but were instead rendered in all caps.
- The
varnameelement should be rendered normally when used inside of acodeblockelement, but it was missing the formatting (in this case, italic).
- The
- In some instances, an entire topic appeared in italic font.
- The following issues with tables:
- The space provided for tables was too small, and tables that were too large to fit displayed with a horizontal scrollbar.
- Tables had centered headers when viewed in Internet Explorer.
Printing
Printing a page using the browser's built-in print option printed the entire page rather than the content pane.
When viewing a topic in Dynamic Documentation and you used your browser's Print option, the area printed included parts of the page that are not what a user typically wants to print, such as the navigation tree, and top banner. Now the printed area includes only the topic's title, body, and breadcrumbs. In addition, large images and tables are made to fit on the printable page without the need for scrolling.
Other fixed issues
- There was no way to connect a topic GUID to its URL, or vice versa. URLs no longer contain GUIDs, which is necessary for debugging purposes.
- The Front Page Management interface was not available.
- Filtered conditions were returned to their default values after the user refreshed the page.
- Publication was personalizable when it shouldn't be.