Automatic decoding of URLencoded cookies

[npicca]

First of all thank you for developing and maintaining this amazing extension :)
However, one thing that always bothered me is the fact that the cookies are displayed "as is", with most special characters URLencoded. This is expecially painful if a JSON is stored in a cookie, making it hard to read.
I tried to fix it by adding an option (disabled by default) which allowed to automatically URL-decode the cookie name and value.
I'm aware of #19 , but I wasn't able to replicate the issue, even with URL-decoding turned on.

I also added the locale strings for it and en, and the other languages should fallback to en.

Let me know if this is acceptable, or if it needs more work :)

[fcapano]

Hi @npicca, thanks for the work and the kind words!
Do you have an example website where I can test this change?

[npicca]

Sure!
I've set up a simple test website, which sets a JSON as a cookie (urlencoded because it contains special values). This is done via javascript because i used a python simpleHTTPserver, but it also applies to cookies set via an header.
If you want to try in the real world, github has a cookie tz, in the format Continent/City (eg Europe/Rome). The slash is usually displayed as %2F, but with my patch it's decoded (aiding readibility).
Let me know if you want to test some more examples :)

[fcapano]

I understand the change now. Unfortunately the change as is is not good because it doesn't just display the values in a friendly format, it also changes the format of the stored cookie.

For instance, your test page creates a cookie with value:
"%7B%22weird_cookie-val%22%3A%22With%3Dspecial%2FCHARS%22%7D".
With your changes enabled, if I open the EditThisCookie popup and click save, the cookie's new value will be:
"{"weird_cookie-val":"With=special/CHARS"}"
which is not what I was expecting.

This is a tricky issue because a cookie might have both url encoded characters and non-url encoded ones. For example this is a valid cookie value: "%7B{". How would you go, then, pretty printing it in the UI but storing the right value when you save it?