Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

Is the change in window.location (square brackets encoded) is a voluntary or involuntary change?

  • 2 antwoorden
  • 1 heeft dit probleem
  • 6 weergaven
  • Laatste antwoord van Nielyr

more options

In Firefox, version prior to 35.0 window.location were returning decoded square brackets (ex.: http://example.org/something[values]) like all other browsers we are supporting for our website. In Firefox 35.0 and 35.0.1, square brackets are encoded (http://example.org/something%5Bvalues%5D). Is this change done voluntary or is it a bug as a side effect of something?

We are using Sammy.js to create route to access different pages of the website, and some routes are broken since version 35 because the square brackets are no more detected by sammy. We can modify the library to decode the URI before doing the comparison, but I will prefer avoid modifying external library.

In Firefox, version prior to 35.0 window.location were returning decoded square brackets (ex.: http://example.org/something[values]) like all other browsers we are supporting for our website. In Firefox 35.0 and 35.0.1, square brackets are encoded (http://example.org/something%5Bvalues%5D). Is this change done voluntary or is it a bug as a side effect of something? We are using Sammy.js to create route to access different pages of the website, and some routes are broken since version 35 because the square brackets are no more detected by sammy. We can modify the library to decode the URI before doing the comparison, but I will prefer avoid modifying external library.

Bewerkt door Nielyr op

Gekozen oplossing

By looking in bug tracking system for Firefox, I found it has been fixed in Firefox 36 and up.

Dit antwoord in context lezen 👍 0

Alle antwoorden (2)

more options

I didn't see anything in the release notes of version 35 that could be related to this.

Bewerkt door Nielyr op

more options

Gekozen oplossing

By looking in bug tracking system for Firefox, I found it has been fixed in Firefox 36 and up.