This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 14071 - Screen.{color,pixel}Depth not sufficiently distinguished
Summary: Screen.{color,pixel}Depth not sufficiently distinguished
Status: RESOLVED DUPLICATE of bug 17522
Alias: None
Product: CSS
Classification: Unclassified
Component: CSSOM View (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Simon Pieters
QA Contact: public-css-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-08 01:17 UTC by Glenn Adams
Modified: 2013-08-08 13:28 UTC (History)
3 users (show)

See Also:


Attachments

Description Glenn Adams 2011-09-08 01:17:50 UTC
the descriptive text regarding Screen.{color,pixel}Depth does not sufficiently distinguish their semantics, and needs to be further elaborated;

furthermore, the statement

"If the output device does not support colors these attributes must return zero."

does not seem correct, at least in the sense that one can have a monochrome device that supports a pixel depth > 1; e.g., a gray-scale screen
Comment 1 Glenn Adams 2012-08-03 05:55:19 UTC
reassign to myself; apparently i am not the default assignee for this component
Comment 2 Simon Pieters 2013-05-14 12:08:13 UTC
(In reply to comment #0)
> the descriptive text regarding Screen.{color,pixel}Depth does not
> sufficiently distinguish their semantics, and needs to be further elaborated;

What should it say?

> furthermore, the statement
> 
> "If the output device does not support colors these attributes must return
> zero."
> 
> does not seem correct, at least in the sense that one can have a monochrome
> device that supports a pixel depth > 1; e.g., a gray-scale screen

https://dvcs.w3.org/hg/csswg/rev/a72a436d37c1
Comment 3 Glenn Adams 2013-06-18 09:23:36 UTC
See also response under https://www.w3.org/Bugs/Public/show_bug.cgi?id=17522. You may want to make one of these bugs a duplicate of the other since they are concerned with the same issue.
Comment 4 Simon Pieters 2013-06-18 10:02:42 UTC

*** This bug has been marked as a duplicate of bug 17522 ***