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.

Avatar for Username

Caută ajutor

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.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

Enable the "calling WebIDL constructors as functions" on the web

  • 1 răspuns
  • 2 au această problemă
  • 2 vizualizări
  • Ultimul răspuns de guigs

formoney000
formoney000
more options

Hi,

I am developing a web application using php and python. After updating the Firefox to the latest version 30.0, some functions on my app do not work anymore. I checked the change logs of Firefox and found out this change: "Disallow calling WebIDL constructors as functions on the web" caused the issue on my tool.

So how can I fix this on the browser side since I cannot change the codes immediately right now?

Also a suggestion: Please reverse this change on the next update of this browser since this will affect my users or else I have to greatly change the codes.

Thanks

Hi, I am developing a web application using php and python. After updating the Firefox to the latest version 30.0, some functions on my app do not work anymore. I checked the change logs of Firefox and found out this change: "Disallow calling WebIDL constructors as functions on the web" caused the issue on my tool. So how can I fix this on the browser side since I cannot change the codes immediately right now? Also a suggestion: Please reverse this change on the next update of this browser since this will affect my users or else I have to greatly change the codes. Thanks

Modificat în de formoney000

Toate răspunsurile (1)

guigs
guigs
more options

Please check out where this is fixed and the Site Compatibility list in the last portion of the bug https://bugzilla.mozilla.org/show_bug.cgi?id=916644