1265175 - opening Troubleshooting info tab misses "acceleratedWindows" string

Status: RESOLVED DUPLICATE of bug 1281785

(Thunderbird :: Mail Window Front End, defect)

Description

[:aceman]

Just open Troubleshooting info in Thunderbird:

Error: NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIStringBundle.GetStringFromName]
Source File: chrome://messenger/content/about-support/gfx.js
Line: 228

The code is:
createHeader(bundle.GetStringFromName("acceleratedWindows"))

There is no "acceleratedWindows" string in c-c or m-c. Maybe it was recently removed?

Comment 1

[Richard Marti (:Paenglab)]

Bug 1263849 removed this and other strings.

Comment 2

[:aceman]

I think this makes all the bottom sections in about:troubleshooting just blank. We should fix this before TB52.

Comment 4

[Richard Marti (:Paenglab)]

What about using the toolkit aboutSupport files and only extend them with the account infos. Then we would be less broken and changes in toolkit would be easier to implement in our files.

Comment 5

[Jorg K (CEST = GMT+2)]

Yes, I think we should leverage as much of FF as we can. Who wants to do it ;-)

Comment 6

[Jorg K (CEST = GMT+2)]

With bug 1281785 landed, Help > Troubleshooting Information looks a whole lot better.

Sections "Graphics" and "Javascript" are now populated, "Accessibility" is partly populated since its running into:

JavaScript error: chrome://messenger/content/about-support/a11y.js, line 19: TypeError: Services.getIntPref is not a function

Or in the error console:
TypeError: Services.getIntPref is not a function  a11y.js:19:19
populateAccessibilitySection   chrome://messenger/content/about-support/a11y.js:19:19
window.onload                  chrome://messenger/content/about-support/init.js:74:3

Filed bug 1302651 for that.

Comment 7

[:aceman]

Thanks for following this and clearing the remaining stuff, Jorg. Looks like our page was quite rotted.

This was a quite visible breakage in the UI so good that is is fixed for TB52.