Closed
Bug 1141112
Opened 10 years ago
Closed 2 years ago
Tooltips are not visible on hover with High Contrast 2#
Categories
(Core :: Widget: Win32, defect, P3)
Tracking
()
RESOLVED
DUPLICATE
of bug 1757797
Accessibility Severity | s2 |
People
(Reporter: vtamas, Unassigned)
References
Details
(Keywords: access, regression, Whiteboard: tpi:+, )
Attachments
(1 file)
(deleted),
image/jpeg
|
Details |
Reproducible on:
Firefox 39.0a1 using Windows 8.1 64bit
STR
1. Right click on desktop -> Personalize.
2. Select High Contrast 2#.
3. Launch Firefox with clean profile.
4. Hover over one of the icons from the Toolbar (e.g.Bookmarks icon).
AR
The tooltips are black and are not visible on hover.
ER
The tooltips are clearly visible on hover.
Additional notes:
- This issue is reproducible on Firefox 39.0a1 (2015-03-08) using Windows 8.1 64bit with High Contrast 2#.
- This issue is not reproducible on Windows 7 x64 and Ubuntu 14.04 32bit.
- I am attaching a screenshot: http://i.imgur.com/msrecI2.jpg
- This is a regression:
Last good revision: b44898282f21
First bad revision: 32c3ccd8946c
Pushlog:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b44898282f21&tochan
ge=32c3ccd8946c
Updated•10 years ago
|
Comment 1•10 years ago
|
||
Do you have a win8 (NOT 8.1) machine to check if this is 8.1-specific?
Flags: needinfo?(vasilica.mihasca)
Comment 2•10 years ago
|
||
Comment 3•10 years ago
|
||
Jim/Masatoshi-san, this is fixed for me locally if I revert the manifest change from firefox.exe.manifest from bug 888870 .
AFAICT GetSystemColor returns the same value with both the working and the breaking manifest. Devtools shows the right color swatches (background-color should be yellow, foreground-color should be black) even in the broken case.
I'm not sure why this is broken. Can either of you investigate further?
Blocks: 888870
Flags: needinfo?(jmathies)
Flags: needinfo?(gijskruitbosch+bugs)
Flags: needinfo?(VYV03354)
Updated•10 years ago
|
Component: Theme → Widget: Win32
Product: Firefox → Core
Comment 4•10 years ago
|
||
I really do not have time to look at this at the moment.
Flags: needinfo?(jmathies)
Reporter | ||
Comment 5•10 years ago
|
||
(In reply to :Gijs Kruitbosch from comment #1)
> Do you have a win8 (NOT 8.1) machine to check if this is 8.1-specific?
I managed to reproduce this issue on Firefox 40.0a1 (2015-04-02) using Windows 8 32-bit and Windows 8 64-bit.
This issue also reproduces on Firefox 4 which means it is a regression.
I will provide you a regression window as soon as possible.
Flags: needinfo?(vasilica.mihasca)
Reporter | ||
Comment 6•10 years ago
|
||
I wanted to investigate it further but I was unable to get the inbound data because there are no build dirs on inbound for these changesets. So, the only regression data remains from m-c ( see comment 0 ).
Comment 7•8 years ago
|
||
Comment 8•8 years ago
|
||
Maybe related:
https://msdn.microsoft.com/en-us/library/hh404233.aspx
> Application manifest. Applications designed to work with the new high
> contrast themes should have an application compatibility section defined
> in their manifest that contains the Windows 8 compatibility GUIDs.
> Otherwise, Windows assumes that the application is designed for an older
> version of Windows and renders the application UI by simulating the
> Windows classic theming model.
https://msdn.microsoft.com/en-us/library/windows/desktop/hh848048(v=vs.85).aspx
> Apps that add support for Windows 8 in their manifest, but do not use
> visual styles for rendering, that is, they hardcode colors or images in
> their apps, might not render correctly in high-contrast themes. Text
> might be difficult to read or images might not appear as they should in
> high contrast mode.
Flags: needinfo?(VYV03354)
Updated•8 years ago
|
Priority: -- → P3
Whiteboard: tpi:+
Comment 10•7 years ago
|
||
We still see this issue on Win10 (see bug 1373184) recently. This breaks the accessibility IMO and I'd like to ask for reconsideration to get it prioritized. Thanks!
Updated•2 years ago
|
Severity: normal → S3
Comment 12•2 years ago
|
||
The severity field for this bug is set to S3. However, the accessibility severity is higher, [access-s2].
:spohl, could you consider increasing the severity?
For more information, please visit auto_nag documentation.
Flags: needinfo?(spohl.mozilla.bugs)
Comment 13•2 years ago
|
||
Morgan, are you able to confirm if this is still an issue?
Flags: needinfo?(spohl.mozilla.bugs) → needinfo?(mreschenberg)
Comment 14•2 years ago
|
||
I keep forgetting to bring my windows laptop into the office 🙃 but I'll check this -- it's on my radar :)
Comment 15•2 years ago
|
||
I think this is a straight up old dupe of bug 1757797 which was recently fixed, so we should forward-dupe to that bug. :-)
Updated•2 years ago
|
Status: NEW → RESOLVED
Closed: 2 years ago
Flags: needinfo?(mreschenberg)
Resolution: --- → DUPLICATE
Updated•1 years ago
|
Whiteboard: tpi:+, [access-s2] → tpi:+,
Updated•1 years ago
|
Accessibility Severity: --- → s2
You need to log in
before you can comment on or make changes to this bug.
Description
•