First-run wizard is incompatible with dark GTK themes

RESOLVED WORKSFORME

Status

Cloud Services
General
--
minor
RESOLVED WORKSFORME
10 years ago
9 years ago

People

(Reporter: Peter Petrov, Unassigned)

Tracking

unspecified
Future
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008061015 Firefox/3.0
Build Identifier: 0.2.0

The first-run wizard has white background, and expects text to be black. But with dark GTK themes the colors are usually reversed - background is dark, text is white. So the first-run wizard displays white text on white background, which is unreadable.

I'm attaching two screenshots which demonstrate the problem.

Reproducible: Always

Steps to Reproduce:

1. Install a dark GTK theme.
2. Start Weave's first-run wizard.
Actual Results:  
Most of the text in the wizard is invisible.

Expected Results:  
Weave should explicitly set the text-color to black. This is an essential rule to follow in general - whenever you set/change the background color/image, you should also set the text color as well.
(Reporter)

Comment 1

10 years ago
Created attachment 327576 [details]
Screenshot 1 which demonstrates the problem
(Reporter)

Comment 2

10 years ago
Created attachment 327578 [details]
Screenshot 2 which demonstrates the problem

Comment 3

10 years ago
Confirmed from here.
It was impossible to see if I accepted the Terms of Service or not except from the Next button changed status (disabled/not disabled)

Comment 4

10 years ago
There is a simple workaround for this, bumping for some future release.

I'll consider any patches, though.
Severity: major → minor
Status: UNCONFIRMED → NEW
Ever confirmed: true
Target Milestone: -- → Future

Updated

9 years ago
Component: Weave → General
Product: Mozilla Labs → Weave
QA Contact: weave → general
We've rewritten this UI at least twice now, so resolving WFM.  Please file a new bug if there is still a problem.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.