String field formatter doesn't apply when highlight was found

[timroes]

When configuring a string field formatter on a field and then search for a value for it, the highlighting of the fields value completely disables the field formatting for that field, e.g. in the following example I've used the decode base64 formatting (which of course doesn't make the most sense in this example):

If you now search for a value, that has results that are highlighted the formatting will completely be disabled for those fields:

I wonder if we can improve that, at least for the simple field formatter (like uppercase/lowercase) where the actual order and length of the transformed string doesn't change. It's of course harder (i.e. not really possible) to do it on the transforms that actually change the string completely (i.e. base64decode, urlparam and shorten). Though I wonder if for those cases we actually want the highlight to appear and the transform not to apply (the way it's now) or rather the opposite: the highlight simply not to appear but the transform still to apply. Not sure if we've ever discussed that really.

[elasticmachine]

Pinging @elastic/kibana-app-services (Team:AppServices)

[elasticmachine]

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

[kertal]

We are closing this issue in order to provide better transparency of priorities. This issue won't be prioritized in the near future. We track it in #163011 for long term planning.