We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

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.

ఇంకా తెలుసుకోండి

https://www.plm.automation.siemens.com/plmapp/se/en_US/online/Shop broken in Firefox 56.x

  • 1 ప్రత్యుత్తరం
  • 1 ఈ సమస్య కలిగినది
  • 2 వీక్షణలు
  • చివరి సమాధానమిచ్చినది jscher2000 - Support Volunteer

more options

In Firefox 56.0.2 and 57.x, browser to

https://www.plm.automation.siemens.com/plmapp/se/en_US/online/Shop

Click on "I’ve already registered for the trial, but I need to download the software" and the form posts to the server when it should not.

Works correctly in Firefox 55.0.3 and previous versions. The bug is easily reproduced.

In Firefox 56.0.2 and 57.x, browser to https://www.plm.automation.siemens.com/plmapp/se/en_US/online/Shop Click on "I’ve already registered for the trial, but I need to download the software" and the form posts to the server when it should not. Works correctly in Firefox 55.0.3 and previous versions. The bug is easily reproduced.

ప్రత్యుత్తరాలన్నీ (1)

more options

It is scripted to post the form, as you can see in the attached screenshots. But the posts are sent to different addresses in Chrome and Firefox.

Google Chrome posts to

https://www.plm.automation.siemens.com/online/Shop?sku=SE788

Firefox posts to

https://www.plm.automation.siemens.com/plmapp/se/en_US/online/Shop

Probably the "on submit" script that constructs the correct address is not running (or not running correctly) in Firefox 56+ but when I look at the error console, nothing jumps out at me at the reason for the problem. The site's developer might be able to spot it quickly in a debugger if you notify them.