Closed Bug 541219 Opened 10 years ago Closed 10 years ago

Drop the word "Beta" from the AAQ Troubleshooting Information description

Categories

(support.mozilla.org :: Knowledge Base Software, task, P1, critical)

task

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jsocol, Assigned: jsocol)

References

()

Details

Attachments

(3 files)

3.6 isn't in beta anymore. We should stop saying Beta on the AAQ.
Based on feedback from Atul and Cheng, this patch adds a version sniff to the AAQ load that will replace the default text (for 3.6) with text targeted at old versions.

Yes, it checks for, literally, "3.6" in the version, but I'd be surprised if we were still using this by the time the next major version bump comes out.

3.6 - *Troubleshooting Information* Copy and paste the information from *Help > Troubleshooting Information*.
<3.6 - *Installed Extensions* Enter the text from the *Tools > Addons > Extensions* panel.
Attachment #422854 - Flags: review?(paulc)
Comment on attachment 422854 [details] [diff] [review]
switch the text, based on Firefox version

Looks good. Tested on Fx3.5.7 and Fx3.6 and noted the difference.
Attachment #422854 - Flags: review?(paulc) → review+
As a side note, there is a hard-coded "Installed Extensions" notification in forumquestion.js that should also be changed, but I will take care of that in bug 541238, and this bug can remain strictly about changing the label for the textarea.
60979.

I'll comment in but 541238, but basically I think the hard-coded stuff should just change to "Troubleshooting Information". It's accurate, if not specific.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
That's r60979. D'oh.
Status: VERIFIED → RESOLVED
Closed: 10 years ago10 years ago
Reopening to commit to branches/1.5.1_temp. Will re-resolve after patches are committed.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
On branch, r62442
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → FIXED
Verified FIXED; retested 3.6/3.5.x, as I did in comment 8.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.