Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Avatar for Username

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Learn More

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

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

  • 1 antwoord
  • 2 hebben dit probleem
  • 5 weergaven
  • Laatste antwoord van 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

Bewerkt door formoney000 op

Alle antwoorden (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