- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Tue, 02 Jan 2018 09:27:37 +0000
- To: public-css-archive@w3.org
> Use case: what shall be rendered: border-width:1.5px? border-width:0.1px? That's a question asking what to do in those cases, not a use case for your "`renderer`" property. [CSS Cascading and Inheritance spec.](https://drafts.csswg.org/css-cascade-4/#actual) says it's up to the user agent what to do with values that can't be displayed in the given environment and uses exactly the example of border widths as an example: > A used value is in principle ready to be used, but a user agent may not be able to make use of the value in a given environment. For example, a user agent may only be able to render borders with integer pixel widths and may therefore have to approximate the used width. Though according to your description, your use case is to give authors a way to unify the rendering across user agents in those cases. Personally, I think rather than introducing a new property the spec. should 1) define that user agents should use antialiasing in those cases and 2) clarify how values should be rounded when user agents don't support antialiasing. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2127#issuecomment-354727915 using your GitHub account
Received on Tuesday, 2 January 2018 09:27:48 UTC