Closed
Bug 462868
Opened 16 years ago
Closed 16 years ago
background-color text attribute being exposed as black when it isn't
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: aaronlev, Assigned: surkov)
References
(Blocks 2 open bugs)
Details
(Keywords: access, verified1.9.1)
Attachments
(2 files, 1 obsolete file)
23 bytes,
text/html
|
Details | |
5.51 KB,
patch
|
aaronlev
:
review+
MarcoZ
:
review+
beltzner
:
approval1.9.1+
|
Details | Diff | Splinter Review |
In many pages we are exposing the background color as black, which makes the text appear to be black on black.
My guess is that we get it wrong when no background color was set by the page.
Assignee | ||
Comment 1•16 years ago
|
||
do not expose text attribute if background-color wasn't specified at all.
Assignee: nobody → surkov.alexander
Status: NEW → ASSIGNED
Attachment #346392 -
Flags: review?(aaronleventhal)
Assignee | ||
Comment 2•16 years ago
|
||
Attachment #346392 -
Flags: review?(marco.zehe)
Comment 3•16 years ago
|
||
Comment on attachment 346392 [details] [diff] [review]
patch
Just for clarification: If the background-color value is missing alltogether, IA2 clients should assume "white" or "transparent", correct? Please explicitly document this in our text attributes doc.
Attachment #346392 -
Flags: review?(marco.zehe) → review+
Updated•16 years ago
|
Keywords: dev-doc-needed
Reporter | ||
Updated•16 years ago
|
Attachment #346392 -
Flags: review?(aaronleventhal) → review+
Reporter | ||
Comment 4•16 years ago
|
||
Actually, I am confused about that too (comment 3).
Alex, I thought we were going to have default values for various text attributes. When the text attribute is not exposed, use the default value.
But here, this is using a different concept. We're saying it means "not specified". But there is a background color that will be used from the user's Firefox or system preferences.
Assignee | ||
Comment 5•16 years ago
|
||
Actually I'm confused as well. Iirc we should expose rgb(r, g, b) but there is no background at all. It's possibly white. But it's not from point of view gecko layout implementation. It's possibly transparent. But it's not because it should mean we should see desktop. Therefore I thought it's possibly good to follow the gecko layout concept: if there is no background then it's nothing to expose, even for default attributes.
Reporter | ||
Comment 6•16 years ago
|
||
We need to get feedback from the AT developers. Check it in as it is and we'll see what people say.
They will not like it if they will want know what the actual background color is currently (and don't care whether it's because its the default color or was set).
Do we do the same for foreground color? What do we do if it was not specified?
Assignee | ||
Comment 7•16 years ago
|
||
(In reply to comment #6)
> Do we do the same for foreground color? What do we do if it was not specified?
No, color is always specified.
Comment 8•16 years ago
|
||
What about if there's no background color specified, get the background color that's set in the operating system's current Display settings? Do we have access to that? I agree with Aaron, we should not expose nothing.
Assignee | ||
Comment 9•16 years ago
|
||
Attachment #346392 -
Attachment is obsolete: true
Attachment #350564 -
Flags: review?(aaronleventhal)
Assignee | ||
Updated•16 years ago
|
Attachment #350564 -
Flags: review?(marco.zehe)
Assignee | ||
Comment 10•16 years ago
|
||
bug 455834 must be duplicate of this bug.
Assignee | ||
Updated•16 years ago
|
Blocks: textattra11y
Updated•16 years ago
|
Attachment #350564 -
Flags: review?(marco.zehe) → review+
Reporter | ||
Updated•16 years ago
|
Attachment #350564 -
Flags: review?(aaronleventhal) → review+
Assignee | ||
Updated•16 years ago
|
Attachment #350564 -
Flags: approval1.9.1?
Assignee | ||
Comment 11•16 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Comment 12•16 years ago
|
||
Verified fixed using Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2a1pre) Gecko/20081211 Minefield/3.2a1pre
Status: RESOLVED → VERIFIED
Assignee | ||
Comment 13•16 years ago
|
||
there is nothing to document (remove 'dev-doc-needed' keyword)
Keywords: dev-doc-needed
Comment 14•16 years ago
|
||
Comment on attachment 350564 [details] [diff] [review]
patch2
a191=beltzner
Attachment #350564 -
Flags: approval1.9.1? → approval1.9.1+
Comment 15•16 years ago
|
||
Pushed on Alexander's behalf in changeset:
http://hg.mozilla.org/releases/mozilla-1.9.1/rev/25612a6d277c
Keywords: fixed1.9.1
Comment 16•16 years ago
|
||
Verified fixed in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20090120 Shiretoko/3.1b3pre
Keywords: fixed1.9.1 → verified1.9.1
You need to log in
before you can comment on or make changes to this bug.
Description
•