It is not actually a display issue as suggested, it is by design where values > 512 bits are truncated. If you wish to have the actual full value, you can always query via the developer tools.
The trimming actually pre-dates the introduction of
text-overflow: ellipsis on the fields (which are quite a nightmare to get right when things start nesting in weird ways) and as a consequence, actually duplicates effort. So basically it ended in a situation where "pretty formatting" was applied in the middle and then again by the rendering engine. Not quite optimal to say the least.
With that in mind, see this PR which actually removes the manual formatting when converting to a hex display, only relying on the builtin browser version.
You would obviously still see ellipsis at the end if it does overflow when something like a hex string is too long, however if you are after the field inspect would work since it is display-only.
For those wanting to scratch an itch: It may actually be quite useful to have a "Copy button" on these output fields, at the very least where
Hash or anything that is not structured in a
toHuman() form is displayed.