We have a URL "protocol" we handle using internal applications. Call it "asdf". E.g.:
<a target="_blank" rel="noopener noreferrer" href="asdf://item/orange">asdf:<wbr>/<wbr>/item<wbr>/orange</a>
If we send the above text as a "text" message via the HipChat API v2, it is correctly identified and converted to a valid, clickable link.
However, if we send it as an "html" message, it is corrupted in any of several ways, depending on how it's sent, but the only one I really EXPECT to work is sending the anchor tag explicitly:
With a payload of:
The result is:
According to the API v2 documentation, this should work:
html - Message is rendered as HTML and receives no special treatment. Must be valid HTML and entities must be escaped (e.g.: '&' instead of '&'). May contain basic tags: a, b, i, strong, em, br, img, pre, code, lists, tables.
But it looks like I'm falling victim to this API footnote:
Invalid HTML tags and attributes will be automatically removed.
How can I keep HipChat from thinking it's smarter than me, especially since the URL-ification works correctly for text messages?
All good things come to an end - thanks to all our customers and partners who have been along the Hipchat and Stride journey with us. As of Feb 15th 2019, Hipchat Cloud and Stride have reached ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events