-
Notifications
You must be signed in to change notification settings - Fork 323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API Products - heavily truncated product description with html tags #2259
Comments
@ZarTrox, thank you for opening this issue. We will triage it within the next few business days. |
Widget: List of products |
Hello @ZarTrox , thank you for reaching out.
And it seems to be displayed ok: Jut to clarify the behavior, the truncation should happen at 250 characters. could you please share one description that gets so heavily truncated as it does in your screenshot? |
String:
Do you need more information? |
This issue is related to managed developer portal. We advise you to create a Azure support request to get assistance on this issue. Please refer to the below link to create a new Azure support request, Please select Problem Type = "Developer Portal" in the request to route it appropriately. |
Bug description
We noticed that our API Product descriptions are heavily truncated for certain products:
After some investigation, we concluded, that it might be due to html tags used in the description.
Without
</br>
tags more text is shown, but it is still heavily truncated.Removing unordered list tags (with list items) shows almost all of the Product description
Removing even hyperlink
<a>
tags from the description results in this:To provide the best description of our products to our customers we rely on using lists, breaks and more html tags. Truncating the text heavily to the extend that on the Products page users cannot even get a short description, and having to navigate to the product itself to read the description, is bad behavior.
Reproduction steps
Expected behavior
Is your portal managed or self-hosted?
Managed
The text was updated successfully, but these errors were encountered: