We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.
For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.
Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.
All projects since 2014-ish have used this idea on displaying "Help Text" for Editors: https://talk.alfnilsson.se/2014/12/18/display-help-text-in-on-page-editing/
- I've worked with 25++ projects, they all use the idea above, from 2014.
Why didnt you keep supporting that idea, instead of this breaking change.
Multiple customers have their own background color and font-size/family for the descriptions, now it's breaking...
Today in CMS 12.9.0 (with a custom css module): https://im.ge/i/OGEzU9
Today in CMS 12.10.0 (clean empty project): https://im.ge/i/OGEHYX
It clutters up the UI, look at all question marks, the UI is full of them! And you also have to click to view descriptions ...
Solution for update 1:
Render the description inside an attribute again.
For the "Top Pane Container Node", render the description on "title" attribute to get the hover effect, less clutter/question marks in the Top Pane
For non "Top Pane Container Node" elements, render them as 'epi-property-description' attribute (instead of the title attribute) to avoid hover effect in browsers. And keep the name same as the css class? Well, up to you. If so I could simply add a custom css module to hide elements with css class 'epi-property-description' element, and still be able to use the 2014 article solution on the 'epi-property-description' attribute, which you set to be equal to 'description'
This would then support "CMS.UI 12.10" question mark solution, and also leave an option with little pain, to support the old way of showing descriptions (tooltips).
I would have just reverted it though, but up to you...
Features like this should go into feature toggling in appSettings.json:
"property-description": "button OR attribute OR all" //or whatever the names you want to give it...