- From: <bugzilla@jessica.w3.org>
- Date: Wed, 29 Jun 2011 21:04:29 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13085 --- Comment #4 from j.chetwynd <j.chetwynd@btinternet.com> 2011-06-29 21:04:28 UTC --- no doubt the alpha case for opacity is most likely to be the popular one currently, see CSS. However it is readily apparent there is an excellent use case for data visualisation with each of RGB. peepo.com provides a simple example using canvas, common to many maps, click on the board and observe the change in red saturation, screengrab: http://www.flickr.com/photos/49932622@N05/5623363217/in/photostream/lightbox/ Screens tend to grow with processor speed, and experience (CSS?) suggests that changing a single component at the browser/graphics chip level would considerably reduce temporal artefacts. perhaps a more complex example might be similar to colour separation as used in printmaking. for instance the opacity of each colour layer may more easily be related to the hue. It is possible to manipulate this all on a pixel basis, it certainly appears slower and more complex than the aformentioned CSS method. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 29 June 2011 21:04:30 UTC