If you have the system settings set to "high contrast & #2 extra large font" and attempt to install firefox you will notice that the first screen "Welcome to Deer Park Alpha" fonts do not inherit the font size that was set. Steps to recreate: 1. Control panel, accessiblity options, adjust the contrast for text and colors on your screen. 2. Click on display tab, check the box for "use high contrast", click on settings button. 3. Pull down and pick "high contrast & #2 extra large font", click on "ok". 4. start the exec for firefox "firefox-1.6a1.en-US.win32.installer.exe. 5. You will notice that the first screen of the install ui doesn't inherit the font size used on the desktop.

Update, I would also like to add that the last dialog does behave correctly either, this is coming from Dan K.

This is bug 287192, it's not just for disability access.

Sorry... this bug was meant to mention that both the system contrast settings and the system font size settings are ignored in two of the screens in the Deer Park setup (install) program. Both the initial "Welcome" screen and the final "Install Complete" screen are displayed with a white background and black text hard-coded. They should be inheriting the system contrast settings: in the original problem statement above, "High Contrast #2" was selected, so the screens should display with a black background and green text. All of the other setup screens inherit the system contrast settings okay. In addition, as the original problem statement mentions, the large fonts are also not inherited. The font size problem exists in all of the setup screens, not just the first and last. This is a section 508 issue (though minor, since only a couple screens are affected, and the install is a one-time-only function). The affected section 508 feature is 1194.21 g.

we'd like to take this, but need to get a better understanding on how hard this will be to fix and what the schedule impact will be (if any), any thoughts?

(In reply to comment #4) > we'd like to take this, but need to get a better understanding on how hard this > will be to fix and what the schedule impact will be (if any), any thoughts? > Do we have anyone who knows the setup code? I suggest we do this post-beta as I anticipate a low-risk fix once someone can get their head around the problem.

dan, can you see if this is enough like the old installer code that you can help out on it? aaron, is this a regression over 1.0.x?

(In reply to comment #6) > aaron, is this a regression over 1.0.x? Asa, I don't know. But for blocking status this, I'm not sure that criteria is the best to go with.

Per discussion with BenG this is not going to be fixable for 1.5

(In reply to comment #8) > Per discussion with BenG this is not going to be fixable for 1.5 Mike, what exactly did we learn in that discussion? What's the reason that it is unfixible for Firefox 1.5?

I'm having the problem in all the setup screens.

Highly visible, first experience with product -> Major

This will be fixed for Firefox 2.0 via the installer rewrite that will use XUL. I don't see a bug for that yet, to mark this dependent on.

I am seeing this same problem in the NSIS-based installer for Firefox 2 (bug 326580). Attaching screenshots.

*** Bug 337138 has been marked as a duplicate of this bug. ***

Bump. These issues still persist in the latest private build of the new NSIS-based installer (see bug 333160 ).

I've done some investigation of this and it won't be a simple thing to fix in the time we have for Firefox 2.0. We are going to have to modify the ui resources that come with NSIS, probably some of the NSIS code itself, and then verify it behaves properly with all locales... not a simple task but we are at least headed down a patch where this is easier to accomplish.

Not going to block if there's upstream issues to solve first, not so happy about this, but its reality.

Yep, this is a PITA that has been around ever since the xpinstall installer was introduced and it is also a problem with the NSIS installer... I am hopeful I'll be able to come up with a fix for Firefox 3.0

*** Bug 345763 has been marked as a duplicate of this bug. ***

*** Bug 287192 has been marked as a duplicate of this bug. ***

*** Bug 225014 has been marked as a duplicate of this bug. ***

What's the status here? Are we able to fix this for 3.0? This has been around quite a while and will no doubt cause some low-vision users not to install the product, not to mention the fact that there are more low-vision users every day.

The fix for this will be implementing the MSI installer which I believe was cut from the PRD.

Specifically, that is bug 231062. Though we could possibly modify NSIS itself the effort to do so is very large with little long term return since we need to implement an MSI for additional reasons so making this depend on bug 231062.

The new stub installer handles this better, but the standard installer is still basically in the same state as described in this bug.

Moving to p3 because no activity for at least 1 year(s). See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information