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!

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“.

Learn More

Unresponsive Script Error when Saving Changed Set in Flickr Organizer

  • 1 Antwort
  • 7 haben dieses Problem
  • 5 Aufrufe
  • Letzte Antwort von blazer869608

more options

I'm getting an unresponsive script error when saving a changed set in the Flickr organizer.

The problem started when using Firefox 3.6.8 or maybe an earlier version. It persists in Firefox 3.6.12

I've noticed the error only appears in the Organizer and only when saving a changed set or saving after deleting a set.

It does indeed save the changed set correctly before crashing.

It is not intermittent and happens every time I perform this save.

The error does not occur in Chrome or Safari.

Examples of the error messages can be found at

http://www.flickr.com/photos/blazer8696/4897580573/

and

http://www.flickr.com/photos/blazer8696/4897656175/

I'm getting an unresponsive script error when saving a changed set in the Flickr organizer. The problem started when using Firefox 3.6.8 or maybe an earlier version. It persists in Firefox 3.6.12 I've noticed the error only appears in the Organizer and only when saving a changed set or saving after deleting a set. It does indeed save the changed set correctly before crashing. It is not intermittent and happens every time I perform this save. The error does not occur in Chrome or Safari. Examples of the error messages can be found at http://www.flickr.com/photos/blazer8696/4897580573/ and http://www.flickr.com/photos/blazer8696/4897656175/

Geändert am von blazer869608

Alle Antworten (1)

more options

Upgrading to 4.0.1 has corrected this problem.