We are running into the problem where people are using the same profile to test different versions of Firefox, the configuration is only set once, when they first install the QAC, so the version of that first Firefox persists. We don't detect it on every run because we didn't want to clobber any settings they had made from the preferences in the case that they are using it to test another product or build. However this is such a rare case and moving to different versions is a much more commmon one. I propose: 1) Re-detecting the platform, os, product, branch, and build id on every start up. 2) Adding a "Keep this configuration when I restart the QAC" checkbox on the preferences that is by default unchecked.
I think that is a solid approach towards addressing this bug/issue. I am curious as to what ctalbert thinks.
Wow, this is a really great use case of how people *really use* the software. I'd have done this (and I think most of QA would have done this) by using different profiles. But I totally agree that this case described in comment 0 is the more frequent and more common case, so we should optimize for that. I like Heather's suggestion in comment 0, let's go that route. Sorry for not responding sooner, I thought that I had responded to this bug, but I guess I didn't.
Created attachment 399684 [details] [diff] [review] patch to update configuration on start-up This patch does everything described in the first comment
Assignee: nobody → harthur
Attachment #399684 - Flags: review?(ctalbert)
Created attachment 401388 [details] [diff] [review] patch to update configuration on start-up minus redundant line Moving review to Aaron, he's tried out the previous patch. This patch is exactly the same as the previous patch, but gets rid of the line that sets the preferences to default on first run (as we are getting it on every run anyways).
Attachment #401388 - Flags: review?(aaron.train) → review+
Comment on attachment 401388 [details] [diff] [review] patch to update configuration on start-up minus redundant line Works great, thanks Heather!
Sending chrome/content/prefs.js Sending chrome/content/prefs.xul Sending chrome/content/qa.js Sending chrome/locale/en-US/qa.dtd Sending defaults/preferences/qa.js Transmitting file data ..... Committed revision 51852.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.