- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Thu, 14 Mar 2019 16:41:03 +0000
- To: public-css-archive@w3.org
> I don't s'pose we'd also be able to solve this hairline value for properties like box-shadow & outline-width, let alone hopeful properties like text-stroke-width(compat) or text-shadow? The `outline-width` property references the [`<line-width>` compound type](https://drafts.csswg.org/css-ui-4/#propdef-outline-width) that is defined for `border-width` and therefore accepts border-width keywords. So it should automatically also get a `hairline` value if it is added as a new keyword. `stroke-width` as defined in SVG doesn't accept keyword values, but there's no reason we couldn't add them (meaning, `thick`, `medium`, `thin`, as well as `hairline`) for [the new module that extends it to CSS text](https://drafts.fxtf.org/fill-stroke/#stroke-width). `box-shadow` and `text-shadow` would be more complicated, since there are many different lengths (offset and expansion/inset) interacting. But maybe it's worth a separate issue to discuss the expected behavior of fine resolution shadow effects — I recently discovered that browsers are very inconsistent in how they handle `text-shadow` offsets of less than 1px (see [Twitter thread with people posting screenshots](https://mobile.twitter.com/AmeliasBrain/status/1105258703878418432)). -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3720#issuecomment-472954755 using your GitHub account
Received on Thursday, 14 March 2019 16:41:04 UTC