@destradafilm Probably not in the near future without sponsorship from a company.

@jackparmer Thanks for your response. What exactly do you mean by sponsorship from a company?

@destradafilm companies can contact us to financially sponsor plotly.js feature development:
https://plotly.typeform.com/to/mH1Cpb

@jackparmer What about adding more basic formatting tags? I currently manually add the following:
strong:"font-weight:bold",
strike:"text-decoration:line-through",
h1:"font-size:2em",
h2:"font-size:1.5em",
h3:"font-size:1.17em",
h4:"font-size:1em",
h5:"font-size:0.83em",
h6:"font-size:0.67em",
p:"padding:0em 1em 0em 1em"

I would like to be able to use flag-icon-css in an annotation which would require the ability to not strip out classes when converting from span to tspan in svg_text_utils

@jonfreedman we could certainly allow class to pass through from the pseudo-html to the svg, my concern (and this applies to some of the other suggested additions as well) is that referencing external content means the plot loses portability, or at least would lose that content if rendered elsewhere. That would be a first for plotly.js, at least as far as the plot's static behavior is concerned.

I see your point, I noticed that the react wrapper exposes style and classname on the parent element, is that a similar blurring of portability?

It would be useful if this applied to tooltips as well. I recently got stuck while trying to include an <img> inside a tooltip in a chart.

Hi - this issue has been sitting for a while, so as part of our effort to tidy up our public repositories I'm going to close it. If it's still a concern, we'd be grateful if you could open a new issue (with a short reproducible example if appropriate) so that we can add it to our stack. Cheers - @gvwilson

Already addressed in #6420