搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

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

  • 2 回覆
  • 1 有這個問題
  • 12 次檢視
  • 最近回覆由 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.

由 Nielyr 於 修改

被選擇的解決方法

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

從原來的回覆中察看解決方案 👍 0

所有回覆 (2)

more options

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

由 Nielyr 於 修改

more options

選擇的解決方法

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