-
Notifications
You must be signed in to change notification settings - Fork 795
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
Collapsible property description markdown does not function as documented #6743
Comments
Hi there @stephen-sherman! Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better. We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.
We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions. Thanks, from your friendly Umbraco GitHub bot 🤖 🙂 |
I have taken the liberty to move this to our UmbracoDocs issues as we need to update the documentation. The correct syntax is to use the <details>
<summary>this is initially shown</summary>
this is initially hidden
</details> This syntax follows the HTML standard of making a collapsible element (MDN). |
Thank you, @stephen-sherman, for bringing this to our attention. We’ve updated the document to ensure it showcases the correct syntax 💪 |
Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)
15.1.0
Bug summary
The Umbraco 15 documentation states that a collapsible property description can be made as follows:
Instead, this results in the preceding block of text being rendered as an
h2
.Specifics
No response
Steps to reproduce
Expected result / actual result
No response
The text was updated successfully, but these errors were encountered: