Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

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

  • 2 respostas
  • 1 tem este problema
  • 1 visualização
  • Última resposta por 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.

Modificado por Nielyr a

Solução escolhida

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

Ler esta resposta no contexto 👍 0

Todas as respostas (2)

more options

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

Modificado por Nielyr a

more options

Solução escolhida

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