That’s overkill if all you want is a label. <raw> was added specifically to allow users to insert html in all kinds of situations… including values inside other controls which you can’t use an HTMLViewer for. Please don’t break this functionality.
Sure Greg, I’d appreciate a Feedback case, as you said. I hate to break things and I’m sorry for causing this issue.
Still, <raw> is not documented, it is completely unexpected and it could change (or not) in the future. I wouldn’t rely on it, when there is a specific control for rendering unescaped HTML.
Whoa wait a sec. This feature was specifically added (more than 5 years ago by me in fact) to allow adding unescaped html into any control. The fact that it’s not documented is Xojo’s issue, and more than a few users rely on its behavior.
FWIW, the fact that it appears in release notes means that it is documented though.
See 2017r1 case #45204 and 35156
That functionality was specifically brought forward to Web 2 at user request.
There is a specific issue with how WebLabel plays with <raw>, but <raw> hasn’t changed globally, and doesn’t necessary have to. @AlbertoD already provided a workaround.
I’ll prepare a Feedback case to improve the documentation on this topic, as isn’t obvious. While it’s handy, it also has implications that needs to be considered by the user.
There is no need to vote to retain this functionality, as isn’t planned to be removed. If in the (not near) future needs to be changed, an alternative will surely be provided (we all need to throw some raw HTML from time to time)
The WebLabel bug needs to be fixed (please shout me if you find this is affecting something else), and the documentation needs to make it clear that <raw> exists.
At the moment, there is no organic or easy way to find info about <raw>, unless you already know it exists and actively search for this tag.
I have no plans to make a big ball out of this, just wanted to know how to handle what was changed and I was not aware of. I know this will be fixed or documented ASAP.
Keep up the good work
The label I’m setting the Text to is used for a simple confirmation, the HTMLViewer would be overkill for such a thing. That’s why I think is awesome for such things.