Extrinsic shareable links render XCM transact calls badly

[seadanda]

OK a bit of a niche, but compare the following screenshots:

renders properly as 0x320360090000714c0500 when I paste it in when I construct the call

But when I share the link I get:

Which seems to try to represent the hex as encoded text? (guess)

Edit: it actually also renders wrong when you paste the full call in the top input box.

[carlosala]

Yeah, that is expected. We attempt to decode it as text, and if successful, we leave it as text. That includes some "non-text" characters as well, like null terminators, etc. We should find a better way of recognising strings, for sure.

[voliva]

For the binary display I added a button to switch between both modes when it detects that it looks like a string (in case it wasn't detected properly): #58

We should probably do the same but for the binary input. I think it's trickier, but it should be doable.