Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

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

  • 2 wótegronje
  • 1 ma toś ten problem
  • 6 naglědow
  • Slědne wótegrono wót 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.

Wót Nielyr změnjony

Wubrane rozwězanje

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

Toś to wótegrono w konteksće cytaś 👍 0

Wšykne wótegrona (2)

more options

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

Wót Nielyr změnjony

more options

Wubrane rozwězanje

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