Pasting tokens is broken when token is improperly formatted

[jestinjht]

A typical use case for jwt.io is to paste a token into the Encoded Value box so that you can see it decoded. Often, the place where you are copying the token from (terminal output, logs, network captures, etc.) does not display them in a correctly formatted way. For example, spaces and line breaks may be added at odd times, depending on the source it was copied from.

In the old UI, this was no big deal. The person pasting the token knew it was improperly formatted, and would simply fix it after pasting. In the new UI, this is broken. The token refuses to paste any further than the first formatting problem, and then an error is displayed. This leaves the user with no option within the site. The workaround is to paste the improperly formatted token into a different edit field (such as a text editor), fix it there, and then re-copy it to the clipboard. This is just silly, considering the Encoded Value box is an editable field. Why not simply allow the formatting to be fixed there?

Any advantages of the new Encoded Value box are far outweighed by the one disadvantage that pasting doesn't work anymore.

[smzajac]

Yes I hate this, I have a token that is just a header and it refuses to allow me to paste, how dumb is that?