Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

HI I have updated my firefox browser to version 29.0.1 , from that time my asp.net applications ajax, jequery , jscript functionality are not working properly.

  • 2 Antworten
  • 2 haben dieses Problem
  • 6 Aufrufe
  • Letzte Antwort von Kohei

himaram
himaram
more options

some of my asp.net code templates are not working (which are integrated with ajax,jquery,javascript) in firefox 29.0.1 . when i select dates and click on 'Go' , it has to update part of the page but its not doing that for some dates before 08/01/2013 (as start date)

Any help would be appreciated

some of my asp.net code templates are not working (which are integrated with ajax,jquery,javascript) in firefox 29.0.1 . when i select dates and click on 'Go' , it has to update part of the page but its not doing that for some dates before 08/01/2013 (as start date) Any help would be appreciated

Alle Antworten (2)

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

Is there a page online demonstrating this problem? I think without taking a look, we might speculate wildly and waste a lot of your time...

One thing that turned on in Firefox 29 is support for <input type="number">. If any of your date fields were using type="number" as a way to be scripted or styled specially, that may no longer work correctly in Firefox 29 and higher.

This article might be useful:

https://developer.mozilla.org/Firefox/Releases/29/Site_Compatibility

Kohei
Kohei
more options

As I wrote in the site compatibility document, there was a JavaScript regular expression bug affecting older versions of jQuery. This issue has been fixed with Firefox 30 so please upgrade and try again.