TSVB custom CSS broken in v8.13.0

[patodevilla]

Kibana version: 8.13.0

Elasticsearch version: 8.13.0

Server OS version:

Browser version: Version 123.0.6312.59 (Official Build) (arm64)

Browser OS version:

Original install method (e.g. download page, yum, from source, etc.): download page

Describe the bug: In a TSVB visualization custom CSS styling appears to be ignored.

Steps to reproduce:

1. Create a TSVB
2. Add some text in Markdown tab
3. Add any css in Panel options tab.

example css:

* {
  background-color: red;
}

Expected behavior: In a TSVB visualization, css added in Panel options tab should be applied

Screenshots (if relevant):

version 8.12.x

version 8.13.0

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context:

[elasticmachine]

Pinging @elastic/kibana-visualizations (Team:Visualizations)

[markov00]

Checked and it doesn't apply the CSS.

The relative code is here

kibana/src/plugins/vis_types/timeseries/public/application/components/vis_types/markdown/vis.js

Lines 72 to 75 in fb19e57

	// wrapping select for markdown body to make sure selector specificity wins over base styles
	css(`.kbnMarkdown__body {
	${model.markdown_css}
	}`)

Looking at the dev tools seems that the CSS is processed, a new emotion class is created and applied on the fly to the markdown body but or the class is wrongly generated and is completely empty or is just not attached to the dom.

[markov00]

hey @elastic/appex-sharedux team I believe this could be caused by this PR #176478
The the CSS is applied to the div container but probably to the change in the markdown component it is not anymore pickedup.

[petrklapka]

@eokoneyo - Another possible regression of the new markdown component?

[stratoula]

@petrklapka yes it seems is the same cause as the other markdown bug.

[eokoneyo]

@eokoneyo - Another possible regression of the new markdown component?

Yes... it's related to the new markdown component

[eokoneyo]

A fix has been made for this issue, it's not very clear how the new markdown caused this issue. I have documented what happens that results in this issue in the PR linked above.

[eokoneyo]

The change that resulted in this issue has been reverted for an expedited resolution here and will be available in the next patch release