Avatar for Username

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Learn More

Тази тема беше архивирана. Моля, задайте нов въпрос ако имате нужда от помощ.

What do I do when Firefox encodes a request incorrectly?

  • 2 отговора
  • 1 има този проблем
  • 1 изглед
  • Последен отговор от agreenseth

agreenseth
agreenseth
more options

Previously, Firefox was able to display context-sensitive Help in a new window. Now, the window opens, but it is blank. The line that is causing the problem is as follows: https:(ourapplicaitondomainname)/onlinehelp/whskin_tw.htm#Views/Views.htm>>cap=CSH>>pan=1 In Firefox, the same line has the same value, only encoded as follows: https:(ourapplicaitondomainname)/onlinehelp/whskin_tw.htm#Views/Views.htm%3E%3Ecap=CSH%3E%3Epan=1 Since the context-sensitive Help appears as expected in other browsers, we feel the problem exists in Firefox. Can you help? Thanks in advance, Ann Greenseth Intermedix

Previously, Firefox was able to display context-sensitive Help in a new window. Now, the window opens, but it is blank. The line that is causing the problem is as follows: https:(ourapplicaitondomainname)/onlinehelp/whskin_tw.htm#Views/Views.htm>>cap=CSH>>pan=1 In Firefox, the same line has the same value, only encoded as follows: https:(ourapplicaitondomainname)/onlinehelp/whskin_tw.htm#Views/Views.htm%3E%3Ecap=CSH%3E%3Epan=1 Since the context-sensitive Help appears as expected in other browsers, we feel the problem exists in Firefox. Can you help? Thanks in advance, Ann Greenseth Intermedix

Всички отговори (2)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
more options

Hi Ann, do you know when (what version) this changed? It might help with researching the reasons for it, if there were reasons.

agreenseth
agreenseth Задаващият въпроса
more options

I can't tell you exactly when it happened. However, one of our Developers rolled Firefox back to 42.0 and discovered we encounter the same problem in that older version.