Closed
Bug 328119
Opened 19 years ago
Closed 19 years ago
Users who are using "high contrast" in Windows cannot select their themes
Categories
(Firefox :: Disability Access, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 328812
People
(Reporter: jnuncus1, Unassigned)
References
()
Details
Attachments
(9 files, 5 obsolete files)
Screenshot hight resolution
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
If "high resolution" feature (Windows TSR) is ON and resident in memory
at the time FFx loads and attempts to execute its graphic instruction set
for a custom theme, the custom theme will NOT display; and only the "default theme" is displayed.
"High resolution" is a Windows feature that is used by almost all visually
impaired Users; it's use, however, is not confined to individuals who are
"severely" visually impaired but, instead, is a widely used feature by
any and all indivisuals who have difficulty in viewing a graphical user
interface.
Affects Users of FFx ver. 1.5 or higher. Problem
did not exist in FFx ver. 1.0.7.
REPRODUCABLE? YES. Every time.
HOW TO REPRODUCE: Install any custom theme (top rated or not)
in FFx ver. 1.5 and above. Exit from FFx. Turn "high resolution"
in Windows Accessability Options (Control Panel) to ON by checking the
box on the "Display" tab. Restart FFx and choose the custom theme.
Restart FFx so theme will take effect. RESULT: only the default
theme displays, although the default theme may in fact exhibit
"some" color-only characteristics of the custom theme you tried
to "apply"/display.
HOW TO PARTIALLY (unsatisfactory) FIX: Turn "high resolution" to OFF
and restart FFx. NOT a good option for the visually impaired
who generally require BOTH "high resolution" AND a hi-contrast
FFx custom theme containing more contrast and sharper delineation
among UI features than are afforded by the default theme.
Specific platform is XP Home (reported by many); but suspect
"any" Windows O/S in which the "high resolution" Windows TSR
for visually impaired users is loaded in memory at the time
FFx is "launched" (point in time when FFx reads its theme
instruction set and attempts to execute the custom theme
graphics code).
Estimated Users affected: literally millions and millions.
Severity and Importance: VERY HIGH. Critical to visually impaired
users inasmuch as users who have visual difficulty in reading or
viewing a GUI REQUIRE "high resolution" in most instances to be able
to use a computer at all; and many users in that category also
use a custom theme that is more easily readable than the FFx
default theme which is not really a hi-res or hi-contrast type
UI.
Suspected Underlying cause: FFx is attempting to execute its code
in a memory address space to which FFx, under Windows O/S pre-emption
hierarchy, has no "rights" to access when a user is using "high
resolution."
Reproducible: Always
Steps to Reproduce:
1. This appears to be an "errant code" problem pursuant to which FFx is
attempting to access a memory address that is already occupied by
other code that is executing and to which memory address, under the
Windows O/S pre-emption rules, FFx has no "right" to access. Therefore
FFx is NOT being allowed by the Windows O/S to execute its custom theme
graphical instruction set, with the result that FFx cannot display the
custom theme. Apparently there is no conflict between the default
theme and the Windows "high resolution" feature (TSR).
2. Turning the high resolution feature OFF in Windows allows the
custom theme to "apply" and "display."
3. What is wrong? Suspect that Windows O/S in this instance is
denying the memory address space, already in use by the high
resolution TSR, to FFx, as it should be doing. FFx is the
culprit here, attemting to execute "errant code" in an
address space that FFx should not be attempting to access.
Again, this was NOT a problem in FFx ver(s). 1.0.7 and
below.
4. Undertake to perform BOTH sets of test steps listed below.
We have found NO instances in which this conflict fails to
Occur on any Windows XP Home Edition machine. We have not,
however tested it with other versions of Windows such as
Windows 2000, Windows 98, or Windows ME.
ADDITIONAL:
Although it may or may not be relevant to your fixing the
apparent conflict in this instance, please be aware that,
when we attempted to choose and display a custom theme with
high resolution turned to ON, the java script console
consistently produced the following set of "messages"
(NOT "errors" but "messages"):
Invalid chrome URI: /
No chrome package registered for
chrome://navigator/locale/navigator.properties .
No chrome package registered for
chrome://navigator-region/locale/region.properties .
No chrome package registered for
chrome://communicator-region/locale/region.properties .
Just note, however, that regardless of what these lines
of java script console messages say, turning "high resolution"
ON and OFF in Windows is the determinative event insofar
as this apparent bug is concerned.
In addition, do not lose sight of the fact that users who have
visual impairments usually desperately need BOTH "high resolution"
AND some custom theme other than the default theme in FFx. They
should not be put to the Hobbsean Choice of having to do
without one to use the other one; and the FFx developers should
not be robbing Peter to pay Paul, as it were.
Literally millions of users will be very appreciative of
the FFx Developers if this bug is fixed prompthly and a
PATCH that will cure it issued quickly.
I will also enclose as a text file my original write up
for the problem before it was determined that the "high resolution"
feature conflict was the source of the problem. That way,
you will be able to see all the relevant settings that existed
in my configuration files while the custom theme was failing
to display.
Actual Results:
1. Install any theme in FFx, version 1.5 or higher.
2. Exit FFx.
3. In Control Panel, go to "Accessability Options" and then to the
"Display" tab.
4. Check the checkbox to switch "high resolution" to "ON."
5. Click "Apply" and "OK," or "OK" to save the setting and
exit the dialog box.
6. "Launch" FFx.
7. Choose "any" theme other than the default theme.
8. Restart Firefox.
9. Result will be that the custom theme does NOT display although it
will appear in FFx "Themes" as being BOTH "installed" and
"applied."
----------------
ADDITIONAL TEST:
----------------
1. Start FFx with a custom theme of your choosing. Suggest
you use Schellen's Modern Pinball theme for this inasmuch
as his theme is a "metallic" color theme that will show
marked differences from the default Windows XP Home
colors.
2. Go to Control Panel and switch the high resolution
feature to ON as above. DO NOT re-start FFx.
NOTE - IMPORTANT: The high resolution feature does in fact
apply to FFx and the custom theme CONTINUES to display without
degredation and at a much higher level of contrast than before
you switched on high resolution.
3. Minimize, but do NOT exit FFx.
NOTE: On your Windows task bar and generally throughout
your Windows interface, the "metallic" color features from
the Modern Pinball theme affect the Windows Desktop color
scheme also. This suggests a memory address conflict.
FFx and Windows hi-contrast are fighting each other.
4. NOW, EXIT and RE-START FFx.
RESULT: Your custom theme no longer appears. Instead,
FFx only displays its default theme.
5. Now, turn OFF your high resolution.
6. Restart FFx.
RESULT: Your custom theme displays again as normal.
Expected Results:
The custom theme will not "display" and ONLY the default
theme appears displayed. Depending upon the custom theme
that was attempted to be displayed, the default theme may
exhibit some of the color characteristics of the custom
theme but will display none of the other graphical features
of the custom theme, such as, for example, buttons, icons,
tab features, sidebar columns, and the like.
The software should have executed the instruction set for the
custom theme's graphics and should have displayed the custom
theme in FFx.
More specifically, the FFx software should NOT have tried to
execute its code in the space already occupied by the
"high resolution" Windows TSR but, instead, should have
used a different memory address.
In short, the FFx core code governing the "display" of
a custom theme should be re-written so that it no longer
conflicts with the "high resolution" "accessability"
feature in Windows XP Home (and most likely all other
versions of Windows that use the same memory address
space as XP Home Edition uses for the high resolution TSR.
NOTE: This problem first appeared in FFx; it also infects
FFx ver. 1.5.0.1. This was NOT a problem in FFx 1.0.7 and
previous.
The attachment named "BUG-328119-Troubleshoot Notes.txt", contains the troubleshooting notes from prior to discovering the conflict between the high resolution Windows feature and Firefox's ability to actually "apply" and "display" an otherwise correctly "installed" theme that was quality control approved for use on the version of FFx upon which the troubleshoot was performed.
This text file also contains various and sundry settings in the FFx configuration files at the time the problem was occurring and the
troubleshoot was underway.
Note: This identical bug affects Thunderbird ver. 1.5 in the identical manner as it affects FFx ver. 1.5 and above.
Please alert the Thunderbird email developers to this bug.
|
||
Comment 3•19 years ago
|
||
That's because the toolbars are also in high resolution I think.
You need to see your buttons :)
A way out is to customize (replace) the icons in the default theme.
|
|
||
Comment 4•19 years ago
|
||
(In reply to comment #3)
> Created an attachment (id=212715) [edit]
> Screenshot hight resolution
>
> That's because the toolbars are also in high resolution I think.
> You need to see your buttons :)
>
Sorry, that's not the reason (thought vaguely it was the wallpaper patch but that's nonsense).
This regressed between 2004090807 and 2004090908.
http://bonsai.mozilla.org/cvsquery.cgi?module=PhoenixTinderbox&date=explicit&mindate=2004-09-08+06%3A00&maxdate=2004-09-09+08%3A00
I'll re-check it if necessary but I have no time anymore now.
|
|
||
Comment 5•19 years ago
|
||
Re-checked and the function never returned.
(In reply to comment #1)
ERRATTA! ERRATTA!
There is a mistake in terminology here. To Correct the
Mistake in Terminology, the term, "high resolution,"
wherever it appears, should be read as "high contrast."
High resolution (number of pixels in the screen) is totally
irrelevant to this bug.
The "High Contrast" Windows Accessability feature
is the program that is conflicting with FFx's
ability to "display" an "installed," custom, theme.
Should I re-submit the bug report? I can copy
and paste the above report into a word processor and
do a search/change from "high resolution" to "high
contrast" and "hi-res" to "high contrast."
What happened was that, at some point in the
Forum thread, the term, "high resolution"
started to be used incorrectly, then we all
started using the incorrect term.Is it possible to
edit the original of a bug report?
Nuncus
> Created an attachment (id=212658) [edit]
> Notes from original troubleshoots on Bug 328119 - FFx Fails to "Apply" an
> "Installed" Theme.
>
> The attachment named "BUG-328119-Troubleshoot Notes.txt", contains the
> troubleshooting notes from prior to discovering the conflict between the high
> resolution Windows feature and Firefox's ability to actually "apply" and
> "display" an otherwise correctly "installed" theme that was quality control
> approved for use on the version of FFx upon which the troubleshoot was
> performed.
>
> This text file also contains various and sundry settings in the FFx
> configuration files at the time the problem was occurring and the
> troubleshoot was underway.
>
CORRECTED BUG REPORT: INTENDED BY ORIGINAL AUTHOR/REPORTER TO REPLACE, IN ALL RESPECTS, THE ORIGINAL BUG 328119 BUG REPORT.
--------------------
SUMMARY:
-------
FFx 1.5.* Cannot "apply"/"Display" "installed" Theme of XP Home Users who Are using "High Contrast" "Accessibility" Feature in Windows.
CORRECTED BUG REPORT: Corrects the term, "high resolution," wherever it appears, to "high contrast" in Bug report 328119.
I hope this is how one corrects a boneheaded mistake like this in a bug
report. If This should be filed as an entirely new bug report, please
email me at the yahoo.com email address, and I will do so.
Nuncus
-------------------
Description: [reply]
Opened: 2006-02-21 15:42 PST
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1)
Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1)
Gecko/20060111 Firefox/1.5.0.1
If "high contrast" feature (Windows TSR) is ON and resident in memory
at the time FFx loads and attempts to execute its graphic instruction set
for a custom theme, the custom theme will NOT display; and only the "default
theme" is displayed.
"High contrast" is a Windows feature that is used by almost all visually
impaired Users; it's use, however, is not confined to individuals who are
"severely" visually impaired but, instead, is a widely used feature by
any and all individuals who have difficulty in viewing a graphical user
interface.
Affects Users of FFx ver. 1.5 or higher. Problem
did not exist in FFx ver. 1.0.7.
REPRODUCABLE? YES. Every time.
HOW TO REPRODUCE: Install any custom theme (top rated or not)
in FFx ver. 1.5 and above. Exit from FFx. Turn "high contrast"
in Windows Accessibility Options (Control Panel) to ON by checking the
box on the "Display" tab. Restart FFx and choose the custom theme.
Restart FFx so theme will take effect. RESULT: only the default
theme displays, although the default theme may in fact exhibit
"some" color-only characteristics of the custom theme you tried
to "apply"/display.
HOW TO PARTIALLY (unsatisfactory) FIX: Turn "high contrast" to OFF
and restart FFx. NOT a good option for the visually impaired
who generally require BOTH "high contrast" AND a hi-contrast
FFx custom theme containing more contrast and sharper delineation
among UI features than are afforded by the default theme.
Specific platform is XP Home (reported by many); but suspect
"any" Windows O/S in which the "high contrast" Windows TSR
for visually impaired users is loaded in memory at the time
FFx is "launched" (point in time when FFx reads its theme
instruction set and attempts to execute the custom theme
graphics code).
Estimated Users affected: literally millions and millions.
Severity and Importance: VERY HIGH. Critical to visually impaired
users inasmuch as users who have visual difficulty in reading or
viewing a GUI REQUIRE "high contrast" in most instances to be able
to use a computer at all; and many users in that category also
use a custom theme that is more easily readable than the FFx
default theme which is not really a hi-contrast type UI.
Suspected Underlying cause: FFx is attempting to execute its code
in a memory address space to which FFx, under Windows O/S preemption
hierarchy, has no "rights" to access when a user is using "high
contrast."
Reproducible: Always
Steps to Reproduce:
1. This appears to be an "errant code" problem pursuant to which FFx is
attempting to access a memory address that is already occupied by
other code that is executing and to which memory address, under the
Windows O/S preemption rules, FFx has no "right" to access. Therefore
FFx is NOT being allowed by the Windows O/S to execute its custom theme
graphical instruction set, with the result that FFx cannot display the
custom theme. Apparently there is no conflict between the default
theme and the Windows "high contrast" feature (TSR).
2. Turning the high contrast feature OFF in Windows allows the
custom theme to "apply" and "display."
3. What is wrong? Suspect that Windows O/S in this instance is
denying the memory address space, already in use by the high
contrast TSR, to FFx, as it should be doing. FFx is the
culprit here, attempting to execute "errant code" in an
address space that FFx should not be attempting to access.
Again, this was NOT a problem in FFx ver(s). 1.0.7 and
below.
4. Undertake to perform BOTH sets of test steps listed below.
We have found NO instances in which this conflict fails to
Occur on any Windows XP Home Edition machine. We have not,
however tested it with other versions of Windows such as
Windows 2000, Windows 98, or Windows ME.
ADDITIONAL:
Although it may or may not be relevant to your fixing the
apparent conflict in this instance, please be aware that,
when we attempted to choose and display a custom theme with
high contrast turned to ON, the java script console
consistently produced the following set of "messages"
(NOT "errors" but "messages"):
Invalid chrome URI: /
No chrome package registered for
chrome://navigator/locale/navigator.properties .
No chrome package registered for
chrome://navigator-region/locale/region.properties .
No chrome package registered for
chrome://communicator-region/locale/region.properties .
Just note, however, that regardless of what these lines
of java script console messages say, turning "high contrast"
ON and OFF in Windows is the determinative event insofar
as this apparent bug is concerned.
In addition, do not lose sight of the fact that users who have
visual impairments usually desperately need BOTH "high contrast"
AND some custom theme other than the default theme in FFx. They
should not be put to the Hobbsean Choice of having to do
without one to use the other one; and the FFx developers should
not be robbing Peter to pay Paul, as it were.
Literally millions of users will be very appreciative of
the FFx Developers if this bug is fixed promptly and a
PATCH that will cure it issued quickly.
I will also enclose as a text file my original write up
for the problem before it was determined that the "high contrast"
feature conflict was the source of the problem. That way,
you will be able to see all the relevant settings that existed
in my configuration files while the custom theme was failing
to display.
Actual Results:
1. Install any theme in FFx, version 1.5 or higher.
2. Exit FFx.
3. In Control Panel, go to "Accessibility Options" and then to the
"Display" tab.
4. Check the checkbox to switch "high contrast" to "ON."
5. Click "Apply" and "OK," or "OK" to save the setting and
exit the dialog box.
6. "Launch" FFx.
7. Choose "any" theme other than the default theme.
8. Restart Firefox.
9. Result will be that the custom theme does NOT display although it
will appear in FFx "Themes" as being BOTH "installed" and
"applied."
----------------
ADDITIONAL TEST:
----------------
1. Start FFx with a custom theme of your choosing. Suggest
you use Schellen's Modern Pinball theme for this inasmuch
as his theme is a "metallic" color theme that will show
marked differences from the default Windows XP Home
colors.
2. Go to Control Panel and switch the high contrast
feature to ON as above. DO NOT re-start FFx.
NOTE - IMPORTANT: The high contrast feature does in fact
apply to FFx and the custom theme CONTINUES to display without
degradation and at a much higher level of contrast than before
you switched on high contrast.
3. Minimize, but do NOT exit FFx.
NOTE: On your Windows task bar and generally throughout
your Windows interface, the "metallic" color features from
the Modern Pinball theme affect the Windows Desktop color
scheme also. This suggests a memory address conflict.
FFx and Windows hi-contrast are fighting each other.
4. NOW, EXIT and RE-START FFx.
RESULT: Your custom theme no longer appears. Instead,
FFx only displays its default theme.
5. Now, turn OFF your high contrast.
6. Restart FFx.
RESULT: Your custom theme displays again as normal.
Expected Results:
When a User installs a custom theme in FFX that in
fact has been cleared as being suitable for use in
the User's version of FFX, the User expects the
FFx software to "display" his selected theme, regardless
of whether he is running the Windows High Contrast
accessibility feature.
In this instance, however, due to the apparent conflict,
the custom theme will not "display" and ONLY the default
theme appears displayed. Depending upon the custom theme
that was attempted to be displayed, the default theme may
exhibit some of the color characteristics of the custom
theme but will display none of the other graphical features
of the custom theme, such as, for example, buttons, icons,
tab features, sidebar columns, and the like.
The software should have executed the instruction set for the
custom theme's graphics and should have displayed the custom
theme in FFx.
More specifically, the FFx software should NOT have tried to
execute its code in the space already occupied by the
"high contrast" Windows TSR but, instead, should have
used a different memory address.
In short, the FFx core code governing the "display" of
a custom theme should be re-written so that it no longer
conflicts with the "high contrast" "accessibility"
feature in Windows XP Home (and most likely all other
versions of Windows that use the same memory address
space as XP Home Edition uses for the high contrast TSR.
NOTE: This problem first appeared in FFx; it also infects
FFx ver. 1.5.0.1. This was NOT a problem in FFx 1.0.7 and
previous.
------- Comment #1 From Nuncus 2006-02-21 16:06 PST [reply] -------
Created an attachment (id=212658) [edit]
Notes from original troubleshoots on Bug 328119 - FFx Fails to "Apply" an
"Installed" Theme.
The attachment named "BUG-328119-Troubleshoot Notes.txt", contains the
troubleshooting notes from prior to discovering the conflict between the high
contrast Windows feature and Firefox's ability to actually "apply" and
"display" an otherwise correctly "installed" theme that was quality control
approved for use on the version of FFx upon which the troubleshoot was
performed.
This text file also contains various and sundry settings in the FFx
configuration files at the time the problem was occurring and the
troubleshoot was underway.
------- Comment #2 From Nuncus 2006-02-21 16:08 PST [reply] -------
Note: This identical bug affects Thunderbird ver. 1.5 in the identical manner
as it affects FFx ver. 1.5 and above.
Please alert the Thunderbird email developers to this bug.
Thanks,
Nuncus
Summary: FFx 1.5.* Cannot "apply"/"Display" "installed" Theme of XP Home Users who Are using "high resolution" in Windows. → FFx 1.5.* Cannot "apply"/"Display" "installed" Theme of XP Home Users who Are using "high contrast" in Windows.
|
||
Comment 8•19 years ago
|
||
Um, no one is going to alert the Thunderbird developers of anything. If you want their attention, file a separate bug.
(In reply to comment #8)
> Um, no one is going to alert the Thunderbird developers of anything. If you
> want their attention, file a separate bug.
>
Thanks for the heads up.
BTW, have I sufficiently corrected my mistaken
use of the word, "resolution," to "contrast" here, or
do I need to simply resubmit as a new bug report?
What do you suggest? It's a fairly major feature bug;
so, if re-filing the report from scratch as a new
bug will help, should I do that, or does that simply
add to the clutter?
Nuncus
|
Reporter | |
Comment 10•19 years ago
|
||
Simply gives the developers a start on "high contrast" accessibility in Windows XP.
|
|
Reporter | |
Comment 11•19 years ago
|
||
This gives the developers mor info on the coding involved in high contrast feature in Windows. Note: Windows sets a system wide bit when high contrast is turned to ON.
|
|
Reporter | |
Comment 12•19 years ago
|
||
Syntax info on coding for high contrast feature in Windows. Perhaps this will help.
|
|
Reporter | |
Comment 13•19 years ago
|
||
Article might be useful to developers in that it contains the Microsoft testing regime for high contrast compatability of apps.
|
|
Reporter | |
Comment 14•19 years ago
|
||
Words searched in Microsoft KB:
accessibility options high contrast
Search string at MSDN for "high contrast" feature in Windows:
http://support.microsoft.com/search/default.aspx?query=accessibility+options+high+contrast&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&ast=8&ast=9&mode=a&spid=1173&x=14&y=10
|
|
Reporter | |
Comment 15•19 years ago
|
||
Note, from Sara Ford's article, Testing for Accessibility, Sara Ford, Microsoft Corporation, March 2004, the effect of switching "High Contrast" to ON in Windows is as follows:
"High Contrast modifies the operating system font size and font colors. When High Contrast is set, the High Contrast OS System bit is set. If you enjoy working outside on a laptop on sunny days, try using High Contrast Black (large) scheme to improve visibility.
The difference between checking the High Contrast check box and manually customizing the display settings is that the OS System bit is set. If the user manually customizes the OS System Colors to look exactly like High Contrast Black (large) scheme, the application must respond just as it would under the High Contrast scheme. This response should occur because all colors are taken from the OS System Settings. "
Thus, this may in fact be not so much a problem as a memory address conflict as it is a failure to program to the proper API's that one programs to in order to accommodate the fact that the High Contrast OS System bit has been set.
The API's and syntax structures are enclosed above in the articles and article excerpts.
Nuncus
|
||
Comment 16•19 years ago
|
||
Ok, found the cause of this issue. Check out:
Bug 239914 When high contrast theme used, automatically ignore author's colors
(https://bugzilla.mozilla.org/show_bug.cgi?id=239914#c16)
Specifically comment #16, where it is described that when the 'OS Accessibility' flag is set, then
the Mozilla applications (all of them!), always revert back to the 'classic' theme.
The 'classic' theme is designed to use the system colours and styling, and the reasoning is that when the 'OS Accessibility' flag is set, that theme should be selected to apply the system colours and styling...
However, as also discussed in that bug, this may be valid for the pages/document, but not to the theme selection, as a user may want to explicitly select another theme (with extra large icons for example).
Furthermore, the way that this feature is hidden: reverting back to 'classic' without any message, not even when someone tries to select another theme, based on an hidden internal OS accessibility flag, is confusing for a lot of people. (as seen by the start of this issue: 'Themes don't apply after install').
I propose to remove this hidden feature, as nowadays by default FF only as the 'classic' theme, so that people without themes, and the flag turned on, are still using 'classic'. But those people, like nuncus himself, want to EXPLICITELY select a specific theme (those that are designed for accessibility!), are now prevented to do so, as there is no way to override this behaviour!
To remove this feature, just remove the 'CheckUseAccessibleSkin' completely from: http://lxr.mozilla.org/mozilla/source/xpfe/bootstrap/nsAppRunner.cpp
Note, this feature may have been applicable when Mozilla by default had two themes installed, of which the 'modern' theme 'not very accessible' (very not ...), so reverting automatically to 'classic' was usefull. But nowadays only the 'classic' (or default theme is distributed). So, when another theme is installed the user explicitly wants to have that theme, but it prevented by this hidden feature. So, give control back to the users, and remove this 'feature'.
Severity: major → normal
Summary: FFx 1.5.* Cannot "apply"/"Display" "installed" Theme of XP Home Users who Are using "high contrast" in Windows. → Users who are using "high contrast" in Windows cannot select their themes
Version: unspecified → 1.5.0.x Branch
|
|
||
Comment 17•19 years ago
|
||
|
|
Reporter | |
Comment 18•19 years ago
|
||
It may well be that the problem here is NOT an address conflict. Upon further reading in the Microsoft materials, the following is contained in the "Remarks" section of the attachment excerpt:
"There is a difference between the High Contrast color
scheme and the High Contrast Mode. The High Contrast
color scheme changes the system colors to colors that
have obvious contrast; you switch to this color scheme
by using the Display Options in the control panel.
The High Contrast Mode, which uses SPI_GETHIGHCONTRAST
and SPI_SETHIGHCONTRAST, advises applications to modify
their appearance for visually-impaired users. It
involves such things as audible warning to users and
customized color scheme (using the Accessibility
Options in the control panel). For more information,
see HIGHCONTRAST. For more information on general
accessibility features, see Accessibility."
See:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sysinfo/base/systemparametersinfo.asp?frame=true&hidetoc=true
(towards end of article).
It seems reasonably clear that the app should be responding to the notification that it receives by virtue of the fact that the OS System bit has been set for High Contrast Mode by "modify[ing] [its] appearance for visually-impaired users;" and the app is not doing this correctly, or, at least is not doing so in a manner that will continue to have the OS allow the app to "display" a theme extension that is riding on the default theme.
Nuncus
|
|
||
Comment 19•19 years ago
|
||
Nuncus, please refrain from adding more text.
The analysis of this issue has been performed, including a possible patch (see comment #16 en #17)
But it is up to the mozilla code reviewers to decide what cause of action will be taken.
|
|
Reporter | |
Comment 20•19 years ago
|
||
Comment on attachment 212911 [details]
Gives Developers more info on high contrast code.
Firefox failed to save the file originally.
See below for the file by the same name.
Attachment #212911 -
Attachment is obsolete: true
|
|
Reporter | |
Comment 21•19 years ago
|
||
Comment on attachment 212912 [details]
Coding structure for high contrast in Windows.
Firefox Failed to save this file originally
and I just now became aware of that fact.
See file below by the same name for the file.
Attachment #212912 -
Attachment is obsolete: true
|
|
Reporter | |
Comment 22•19 years ago
|
||
Comment on attachment 212912 [details]
Coding structure for high contrast in Windows.
Firefox Failed to save this file originally
and I just now became aware of that fact.
See file below by the same name for the file.
|
|
Reporter | |
Comment 23•19 years ago
|
||
Comment on attachment 212913 [details]
MSDN Guidelines for TESTING high contrast compataility in an app.
Firefox Failed to save this file originally
and I just now became aware of that fact.
See file below by the same name for the file.
Attachment #212913 -
Attachment is obsolete: true
|
|
Reporter | |
Comment 24•19 years ago
|
||
Comment on attachment 212942 [details]
Contains SystemParametersInfon function that retrieves or sets the value of one of the system-wide parameters.
Firefox Failed to save this file originally
and I just now became aware of that fact.
See file below by the same name for the file.
Attachment #212942 -
Attachment is obsolete: true
|
|
Reporter | |
Comment 25•19 years ago
|
||
Comment on attachment 212911 [details]
Gives Developers more info on high contrast code.
Firefox Failed to save this file originally
and I just now became aware of that fact.
See file below by the same name for the file.
|
|
Reporter | |
Comment 26•19 years ago
|
||
|
|
Reporter | |
Comment 27•19 years ago
|
||
|
|
Reporter | |
Comment 28•19 years ago
|
||
|
|
Reporter | |
Comment 29•19 years ago
|
||
|
|
Reporter | |
Comment 30•19 years ago
|
||
|
|
Reporter | |
Comment 31•19 years ago
|
||
|
||
Comment 32•19 years ago
|
||
Duped upstream to Core bug 328812 to escape the noise here.
Nuncus, please refrain from adding unnessary attachments/comments to bug 328812.
*** This bug has been marked as a duplicate of 328812 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
|
|
||
Updated•19 years ago
|
Attachment #212936 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•