- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Dec 2017 12:24:33 +0000
- To: public-css-archive@w3.org
> I propose: > > renderer: aliased | antialiased; > > if developer will want to work with subpixels, he/she can enable renderer:antialiased and borders, width etc. will be rendered with antialiasing. > > How about this solution? What's the use case for this proposal? Note that there are already [`text-rendering`](https://svgwg.org/svg2-draft/painting.html#TextRenderingProperty) and [`image-rendering`](https://drafts.csswg.org/css-images-3/#the-image-rendering) to improve speed or visual optimization. > For aliasing mode there shall be in future defined one algorithm or added new values for "renderer" defining bahaviours from FF, IE and Cr. It would surely be enough to have one value for aliasing mode. Two general notes: IE is dead. You mean Edge. Keep in mind that user agents interpreting CSS are not restricted to web browsers, and not just those three. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2127#issuecomment-354280593 using your GitHub account
Received on Thursday, 28 December 2017 12:24:40 UTC