I found a work around for people affected by this bug. 1) Reproduce the error and leave the error dialog open. 2) Open another QAC window and use that instead.
Sounds like an unusual error that prevents people from really using the product. P2
Priority: -- → P2
Created attachment 349533 [details] [diff] [review] patch v1 Ok, looks like this happened because we changed the JSON parsing under the covers. It's now getting back a string where before it was evidently getting back an int. Code will now handle both cases (firefox 2 & onward).
Assignee: nobody → ctalbert
Status: NEW → ASSIGNED
Comment on attachment 349533 [details] [diff] [review] patch v1 Speaking of JSON, this will likely be of interest when refactoring commences: https://developer.mozilla.org/En/Updating_extensions_for_Firefox_3.1#JSON
Attachment #349533 - Flags: review?(brian) → review+
(In reply to comment #4) > (From update of attachment 349533 [details] [diff] [review]) > Speaking of JSON, this will likely be of interest when refactoring commences: > > https://developer.mozilla.org/En/Updating_extensions_for_Firefox_3.1#JSON Indeed that might be an issue, but so far, this patch works on 3.1. That leaves open a distinct possibility that we aren't using JSON in the "standard" manner, and so might open us to issues down the road. Or it might mean that we're just not doing anything too terribly complicated with it. Good chance either way, we should investigate that during the refactoring. Checked in: Checking in chrome/content/litmus.js; /cvsroot/mozilla/testing/extensions/community/chrome/content/litmus.js,v <-- litmus.js new revision: 1.19; previous revision: 1.18 done
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.