Open
Bug 798866
Opened 12 years ago
Updated 2 years ago
Stub Installer: checkboxes do not use themed controls
Categories
(Firefox :: Installer, defect, P5)
Tracking
()
NEW
People
(Reporter: sstangl, Unassigned)
References
Details
(Keywords: polish, Whiteboard: [stubv3=])
Attachments
(1 file)
(deleted),
image/png
|
Details |
Theme-specific controls on Windows are missing; instead, "Windows Classic" controls are used, which look extremely outdated, out-of-place, and plain bad.
Instead, we should make the installer fit into the local Windows theme.
Snapshot attached.
Reporter | ||
Comment 1•12 years ago
|
||
Additionally, the bold, oversized "Make Nightly my default browser" text does not follow the theme either.
Updated•12 years ago
|
Updated•12 years ago
|
Blocks: StubInstaller
Comment 2•12 years ago
|
||
Just the checkboxes, the buttons are correctly themed.
Comment 3•12 years ago
|
||
That is a workaround to allow us to control the text color of the control. If we were to go with the local Windows theme we could do this but it would require using the background colors specified by the theme so we wouldn't be able to specify that color as well as other colors. We should be able to override the WM_PAINT message and paint it ourselves but that would add complexity and increase the stub installers size.
cc'ing UX folk to get their input on the above
Summary: Stub Installer: Does not use themed controls → Stub Installer: checkboxes do not use themed controls
Comment 4•12 years ago
|
||
Note that the attached screenshot appears to be in a higher DPI mode, possibly 150% or 200%. I noticed this because the application close buttons are much larger than a 100% DPI view.
Comment 5•12 years ago
|
||
Can we use WS_EX_TRANSPARENT for the checkbox control to get it to blend properly?
Comment 6•12 years ago
|
||
(In reply to Jim Mathies [:jimm] from comment #5)
> Can we use WS_EX_TRANSPARENT for the checkbox control to get it to blend
> properly?
Not without controlling WM_PAINT (see comment #3)
Comment 7•12 years ago
|
||
(In reply to Robert Strong [:rstrong] (do not email) from comment #6)
> (In reply to Jim Mathies [:jimm] from comment #5)
> > Can we use WS_EX_TRANSPARENT for the checkbox control to get it to blend
> > properly?
> Not without controlling WM_PAINT (see comment #3)
I guess I don't understand what we are doing here. The checkbox should render correctly if common controls manifest is loaded into the exe. They can be transparent so the background shouldn't be an issue. If the text is the problem you could place a new label next to the checkbox instead. It looks like we are already handling text color / boldness in other labels.
Comment 8•12 years ago
|
||
(In reply to Jim Mathies [:jimm] from comment #7)
> (In reply to Robert Strong [:rstrong] (do not email) from comment #6)
> > (In reply to Jim Mathies [:jimm] from comment #5)
> > > Can we use WS_EX_TRANSPARENT for the checkbox control to get it to blend
> > > properly?
> > Not without controlling WM_PAINT (see comment #3)
>
> I guess I don't understand what we are doing here. The checkbox should
> render correctly if common controls manifest is loaded into the exe. They
> can be transparent so the background shouldn't be an issue. If the text is
> the problem you could place a new label next to the checkbox instead. It
> looks like we are already handling text color / boldness in other labels.
NSIS handles it internally and we would need to override it because of that
Updated•12 years ago
|
Whiteboard: [stub=]
Updated•12 years ago
|
Assignee: nobody → robert.bugzilla
Status: NEW → ASSIGNED
Updated•11 years ago
|
Whiteboard: [stub=] → [stubv2=]
Updated•10 years ago
|
Whiteboard: [stubv2=] → [stubv3=]
Comment 9•10 years ago
|
||
It's unlikely that I will get to work on this in the next two weeks, so unassigning myself for now.
Assignee: robert.strong.bugs → nobody
Updated•8 years ago
|
Priority: -- → P3
Updated•7 years ago
|
Priority: P3 → P5
Updated•7 years ago
|
Severity: normal → trivial
Status: ASSIGNED → NEW
Updated•2 years ago
|
Severity: trivial → S4
You need to log in
before you can comment on or make changes to this bug.
Description
•