Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why only for Canvas? #14

Open
lrosenthol opened this issue May 17, 2017 · 3 comments
Open

Why only for Canvas? #14

lrosenthol opened this issue May 17, 2017 · 3 comments

Comments

@lrosenthol
Copy link

How would these same concepts also be applied to standard HTML elements (eg. text) or SVG or MathML or any other content found in the Open Web Platform? Why not do this in CSS, where everyone/thing would benefit?

@junov
Copy link
Member

junov commented May 17, 2017

I think what you are looking for is in CSS color module level 4. The CSS color() function will allow colors to be specified in any color space. See: https://drafts.csswg.org/css-color-4/#funcdef-color

In HTML+CSS there is no direct control over the rendering pipeline. The CSS+HTML provide a language for describing document content, and browsers have to figure out the optimal way to display it on the user's hardware (display or printing device). The choice of intermediate colorspace, pixel resolution and color bit depths are automatic.

Canvas, on the other hand is not a document description API. That is why the proposal found here is orthogonal. The canvas provides an isolated rendering environment, where it makes sense to provide more low level controls for configuring the rendering pipeline.

@lrosenthol
Copy link
Author

lrosenthol commented May 18, 2017 via email

@junov
Copy link
Member

junov commented May 18, 2017

cc @bfgeek

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants