Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Learn More

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

  • 2 trả lời
  • 1 gặp vấn đề này
  • 12 lượt xem
  • Trả lời mới nhất được viết bởi 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.

Được chỉnh sửa bởi Nielyr vào

Giải pháp được chọn

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

Đọc câu trả lời này trong ngữ cảnh 👍 0

Tất cả các câu trả lời (2)

more options

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

Được chỉnh sửa bởi Nielyr vào

more options

Giải pháp được chọn

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