Kibana version:
v8.13.2
Elasticsearch version:
v8.13.2
Server OS version:
cloud
Browser version:
Version 124.0.6367.60 (Official Build) (arm64)
Browser OS version:
14.4.1 (23E224)
Original install method (e.g. download page, yum, from source, etc.):
cloud
Describe the bug:
In dev tools, if right-to-left arabic text is used as a token in a sparse_embedding.embedding field, the text is displayed incorrectly. The underlying API returns the text correctly, this is solely a UI issue.
Steps to reproduce:
Set up an inference endpoint with ELSER or another sparse embedding model
Perform inference with that model on arabic text (for example: "وفوكو-جي هو معبد بوذي في مدينة نارا، محافظة نارا اليابان.")
View the response elements with arabic characters, the characters are on the right side rather than the left side, and the numbers are on the left side rather than the right side.
Expected behavior:
Arabic characters are formatted in the same way as non-arabic text.
Screenshots (if relevant):
Incorrect:
Kibana version: v8.13.2 Elasticsearch version: v8.13.2 Server OS version: cloud Browser version: Version 124.0.6367.60 (Official Build) (arm64) Browser OS version: 14.4.1 (23E224) Original install method (e.g. download page, yum, from source, etc.): cloud Describe the bug: In dev tools, if right-to-left arabic text is used as a token in a sparse_embedding.embedding field, the text is displayed incorrectly. The underlying API returns the text correctly, this is solely a UI issue.
Steps to reproduce:
"وفوكو-جي هو معبد بوذي في مدينة نارا، محافظة نارا اليابان."
)Expected behavior: Arabic characters are formatted in the same way as non-arabic text. Screenshots (if relevant): Incorrect:
Expected:
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
Any additional context: