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

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.

Learn More

This thread was archived. اگر به کمک نیاز دارید لطفاً یک سؤال بپرسید.

Unresponsive Script Error when Saving Changed Set in Flickr Organizer

  • 1 پاسخ
  • 7 have this problem
  • 5 views
  • آخرین پاسخ توسّط blazer869608

blazer869608
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/

Modified by blazer869608

All Replies (1)

blazer869608
blazer869608 Question owner
more options

Upgrading to 4.0.1 has corrected this problem.