Loosen requirements for base64 decoding

[kimipsen]

Vote on this issue by adding a 👍 reaction.
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Is your feature request related to a problem? Please describe.
When pasting base64 encoded strings, often it won't decode these, unless I manually pad the ending with '='.

Describe the solution you'd like
It would improve usability if the tool automatically tried padding until the string became a valid/strict base64 string.

Describe alternatives you've considered
Consider showing a warning when failing to decode a string, as it currently is rather difficult to see whats happening.

[Regenhardt]

I could imagine adding this real quick, seems like a good first issue?

[AHollowedHunter]

I have been playing around with this myself, I've added automatic padding conditions but was also looking at implementing an InfoBar below the input box which can be used to provide feedback to the user if the input is invalid or has been automatically padded.

[i3anaan]

Thought the decoding was simply broken, turns out it was missing the = padding. A warning would be much appreciated at the least.
For the record, this was the string I tried to decode: TWFsd2FyZQ