Closed Bug 603151 Opened 14 years ago Closed 14 years ago

Native-themed buttons on the tabs inside Add-ons Manager appear as plain text

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
minor

Tracking

()

RESOLVED DUPLICATE of bug 603049

People

(Reporter: at.light, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0b8pre) Gecko/20101009 Firefox/4.0b8pre Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0b8pre) Gecko/20101009 Firefox/4.0b8pre The "Try Again" button that appears on HTTP error pages (working offline, DNS error, etc.) loses its button appearance inside the embedded browser used by the "Get Add-ons" tab of the Add-ons Manager. The words "Try Again" are displayed as plain text, and it doesn't look clickable. Reproducible: Always Steps to Reproduce: 1. clear cache (Tools>Options>Advanced>Network>Clear cache) 2. File>Work Offline or Minefield Button>Developer>Work Offline 3. Open Add-ons Manager 4. Navigate to the "Get Add-ons" page. 5. Observe the error page that appears. Actual Results: * On Windows XP Luna theme, no button is drawn. The words "Try Again" appear correctly, and the area is still clickable (and still works), but it doesn't look clickable. * On Windows 7 Aero with Direct2D, the button is drawn correctly. Expected Results: The button is drawn correctly.
Summary: "Try Again" button on HTTP error page inside Add-ons Manager appears as plain text → Native-themed buttons on the tabs inside Add-ons Manager appear as plain text
Actually, this occurs with all native-themed buttons inside the Add-ons Manager, like the "Disable" and "Remove" buttons on the "Extensions" page. Only occurs on my Windows XP system, though.
(In reply to comment #1) > Actually, this occurs with all native-themed buttons inside the Add-ons > Manager, like the "Disable" and "Remove" buttons on the "Extensions" page. Only > occurs on my Windows XP system, though. This bit at least is bug 603049
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.