搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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

  • 2 个回答
  • 1 人有此问题
  • 6 次查看
  • 最后回复者为 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.