[Search] fix: FormattedMessage rendering escaped HTML instead of markup

[seialkali]

Summary

After upgrading to react-intl@6.6.6, <FormattedMessage> no longer renders raw HTML when returning strings from value formatters. Previously, returning a string like "<strong>...</strong>" would be interpreted as HTML and rendered. In v6, all strings are escaped for safety, and only React elements are rendered as markup.

As a result, the PagingInfoView component which uses, <FormattedMessage>, was displaying <strong> tags as plain text instead of styled markup on the Docs Explorer page. This has been fixed by updating the strong property in <FormattedMessage> to return a React element.

Before

After

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
• This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
• Flaky Test Runner was used on any tests changed
• The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
• Review the backport guidelines and apply applicable backport:* labels.

Release note

Fixes the Docs Explorer paging info to correctly render bold text. After upgrading to react-intl@6.6.6, the <FormattedMessage> component escaped HTML returned from value formatters, causing <strong> tags to appear as plain text. The component now uses React elements to render the bold text properly.

[wildemat]

Do all open backport versions have this updated react-intl version?

[seialkali]

Do all open backport versions have this updated react-intl version?

@wildemat Good question! I'm not entirely sure. As this bug goes all the way back to v8.15, I asked @TattdCodeMonkey how far back I should backport and he suggested I use the backport:all-open tag. @TattdCodeMonkey how would we be able to tell how far back the open backport versions go?

[wildemat]

As this bug goes all the way back to v8.15, I asked @TattdCodeMonkey how far back I should backport and he suggested I use the backport:all-open tag

Good enough for me!

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: f14f17c

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
enterpriseSearch	1.1MB	1.1MB	+3.0B

Saved Objects .kibana field count

Every field in each saved object type adds overhead to Elasticsearch. Kibana needs to keep the total field count below Elasticsearch's default limit of 1000 fields. Only specify field mappings for the fields you wish to search on or query. See https://www.elastic.co/guide/en/kibana/master/saved-objects-service.html#_mappings

id	before	after	diff
_data_stream_timestamp	1	-	-1
_doc_count	1	-	-1
_ignored_source	1	-	-1
_index_mode	1	-	-1
_inference_fields	1	-	-1
_tier	1	-	-1
apm-custom-dashboards	5	-	-5
apm-server-schema	2	-	-2
apm-service-group	5	-	-5
application_usage_daily	2	-	-2
config	2	-	-2
config-global	2	-	-2
coreMigrationVersion	1	-	-1
created_at	1	-	-1
created_by	1	-	-1
entity-definition	9	-	-9
entity-discovery-api-key	2	-	-2
event_loop_delays_daily	2	-	-2
favorites	4	-	-4
file	11	-	-11
file-upload-usage-collection-telemetry	3	-	-3
fileShare	5	-	-5
infra-custom-dashboards	4	-	-4
infrastructure-monitoring-log-view	2	-	-2
intercept_trigger_record	5	-	-5
legacy-url-alias	7	-	-7
managed	1	-	-1
ml-job	6	-	-6
ml-module	13	-	-13
ml-trained-model	7	-	-7
monitoring-telemetry	2	-	-2
namespace	1	-	-1
namespaces	1	-	-1
observability-onboarding-state	2	-	-2
originId	1	-	-1
product-doc-install-status	7	-	-7
references	4	-	-4
sample-data-telemetry	3	-	-3
security-ai-prompt	8	-	-8
slo	11	-	-11
space	5	-	-5
synthetics-monitor	34	-	-34
synthetics-monitor-multi-space	34	-	-34
tag	4	-	-4
type	1	-	-1
typeMigrationVersion	1	-	-1
ui-metric	2	-	-2
updated_at	1	-	-1
updated_by	1	-	-1
upgrade-assistant-ml-upgrade-operation	3	-	-3
upgrade-assistant-reindex-operation	3	-	-3
uptime-synthetics-api-key	2	-	-2
url	5	-	-5
usage-counters	2	-	-2
total			-246

[kibanamachine]

Starting backport for target branches: 8.18, 8.19, 9.0, 9.1

https://github.com/elastic/kibana/actions/runs/17487444787

[kibanamachine]

💚 All backports created successfully

Status	Branch	Result
✅	8.18
✅	8.19
✅	9.0
✅	9.1

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation