Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

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

  • 2 wotmołwje
  • 1 ma tutón problem
  • 3 napohlady
  • Poslednja wotmołwa wot 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.

Wot Nielyr změnjeny

Wubrane rozrisanje

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

Tutu wotmołwu w konteksće čitać 👍 0

Wšě wotmołwy (2)

more options

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

Wot Nielyr změnjeny

more options

Wubrane rozrisanje

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