חיפוש בתמיכה

יש להימנע מהונאות תמיכה. לעולם לא נבקש ממך להתקשר או לשלוח הודעת טקסט למספר טלפון או לשתף מידע אישי. נא לדווח על כל פעילות חשודה באמצעות באפשרות ״דיווח על שימוש לרעה״.

מידע נוסף

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

  • 2 תגובות
  • 1 has this problem
  • 1 view
  • תגובה אחרונה מאת 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.

Read this answer in context 👍 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.