Comment 16 for bug 308397

(In reply to comment #13)
> Confirming that a patch for this problem should interpolate the installation
> locale to match the spec. As comment #12 mentions, bug 430120 contains the
> rational for having these extra fields in the URL.
>
> The parser expects a legitimate @AB_CD@ code, but it special cases the
> chrome:// value using a gawd awful complicated regex. That workaround would
> break if you tried to do something like adding escaping to the URL instead, so
> if we do end up adding any new escaping to the URL, we need to open a separate
> bug for Metrics to track that.

Presumably if we take a patch for this bug (getting rid of the chrome url from the locale and using a proper locale code) then adding escaping shouldn't actually affect anything.