Avatar for Username

ค้นหาฝ่ายสนับสนุน

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

เรียนรู้เพิ่มเติม

หัวข้อนี้ถูกเก็บถาวรแล้ว โปรดถามคำถามใหม่หากคุณต้องการความช่วยเหลือ

Have a DigiCert signed .jar-doesn't work in V53, does work in IE 11& V52. Firefox is shorting the includes path with a 404 error under Inspector, needs fixing!

  • 1 การตอบกลับ
  • 1 คนมีปัญหานี้
  • 15 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย Kohei

taxvalues
taxvalues
more options

I have a DigiCert Code signed .jar file that doesn't work in V53 but does work in IE 11& V52. Firefox ESR. Firefox is shorting the location of the includes path by ones level for the .jar with a 404 error under Inspect Element->Network. This appears to be fault in the browser and needs fixing. It also somewhat weird that the .jar file is being shown as an html file and not a script. Something is not right in the V53 version as the identical code and certificate store runs under Internet Explorer and also in Firefox V52 ESR. The issue is both on Windows 7 and Windows 10 machines

Without a correction, I have customers that prefer to use Firefox but this fault is making it impossible for me to use V53.

I have a DigiCert Code signed .jar file that doesn't work in V53 but does work in IE 11& V52. Firefox ESR. Firefox is shorting the location of the includes path by ones level for the .jar with a 404 error under Inspect Element->Network. This appears to be fault in the browser and needs fixing. It also somewhat weird that the .jar file is being shown as an html file and not a script. Something is not right in the V53 version as the identical code and certificate store runs under Internet Explorer and also in Firefox V52 ESR. The issue is both on Windows 7 and Windows 10 machines Without a correction, I have customers that prefer to use Firefox but this fault is making it impossible for me to use V53.

การตอบกลับทั้งหมด (1)

Kohei
Kohei
more options

This is probably Bug 1361688 which has already been fixed with Firefox 54.