Prohledat stránky podpory

Vyhněte se podvodům. Za účelem poskytnutí podpory vás nikdy nežádáme, abyste zavolali nebo poslali SMS na nějaké telefonní číslo nebo abyste sdělili své osobní údaje. Jakékoliv podezřelé chování nám prosím nahlaste pomocí odkazu „Nahlásit zneužití“.

Zjistit více

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

  • 2 odpovědi
  • 1 má tento problém
  • 6 zobrazení
  • Poslední odpověď od 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.

Upravil uživatel Nielyr dne

Zvolené řešení

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

Přečíst dotaz v kontextu 👍 0

Všechny odpovědi (2)

more options

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

Upravil uživatel Nielyr dne

more options

Zvolené řešení

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