That is old timey paranoia: in the olden days there were cases according to spec where URLs in HTML (or was it XHTML) should technically HTML encode the & separators, and that string if read in JS would still have the &amp; in them. But I will remove it since we do not exercise it in our code, and can always add it back if we actually hit that probably unlikely scenario.