If a URL contains an ampersand, the ampersand is not encoded as & when the link is output. This breaks XHTML validation. I've wrapped the URL generation in an htmlentities() call, but this will break URLs where ampersands were entered in entity form in the first place, i.e. my solution will encode [?:http://url?first=1&second=2 link] correctly, but doubly encode [?:http://url?first=1&second=2 link], incorrectly.

Any ideas for a better solution?

Comments

duaelfr’s picture

duaelfr
he/him
Primary language French
Location Montpellier, France
commented
Status: Active » Closed (won't fix)

This version of Context links is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.

This issue has been automagically closed by a script.