Bookmark CSS in new v11.2 set to `nowrap` which hinding bookmark content and unble to read bookmark

[dgosai]

WebViewer Version:
11.2.0 or 11.3.0

Do you have an issue with a specific file(s)? No
Can you reproduce using one of our samples or online demos? YES
Are you using the WebViewer server? NO
Does the issue only happen on certain browsers? NO
Is your issue related to a front-end framework? YES
Is your issue related to annotations? NO

Please give a brief summary of your issue:
(Think of this as an email subject)
In Earlier verion of WebViewer Bookmark text was set to 'wrap` but in latest version it set with fixed height of 24 px and white-space: nowrap; due to that cant able to read Bookmark.

Can you guide me how to overwrite this css class or how can I solve this issue?

Please describe your issue and provide steps to reproduce it:
(The more descriptive your answer, the faster we are able to help you)

Any Long text bookmark will give this issue.

Please provide a link to a minimal sample where the issue is reproducible:

[luke.dam]

Hello Dhanesh,

Thank you for contacting WebViewer Forums.

I was able to confirm that the wrapping for the bookmark text was changed. I have notified our development team on this issue. The following CSS properties fixes this issue:

Regards,
Luke

[dgosai]

Hey Luke,

Thanks for your reply. I already tried custom css through css file but its not appying any custom css on WebViewer.

Can you guide me how to apply custom css?

Thanks & regards,
Dgosai

[luke.dam]

Hello Dhanesh,

Thank you for your reply.

You can grab the element and apply CSS directly for example:

document.getElementById('wc-viewer').shadowRoot.querySelector('div.panel-list-description')

This element will only exist once the thumbnailsPanel is opened. You can use the “visibilityChanged” event listener to accomplish this.

Keep in mind that this is an experimental workaround and the bug has been reported to the development team for an official fix. Thank you.

Regards,
Luke

[dgosai]

Hi Luke,

This is working now with your solution. But this is temp work around.

Please let dev team know that this is know issue and fix it in next release so we can remove this temp code.

Thanks for your quick help.