- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Fri, 8 Apr 2016 11:19:13 -0700
- To: fantasai <fantasai.lists@inkedblade.net>
- Cc: Mats Palmgren <mats@mozilla.com>, www-style list <www-style@w3.org>
On Fri, Apr 8, 2016 at 10:02 AM, fantasai <fantasai.lists@inkedblade.net> wrote: > On 04/08/2016 12:11 PM, Tab Atkins Jr. wrote: >> >> On Fri, Apr 8, 2016 at 8:44 AM, Mats Palmgren <mats@mozilla.com> wrote: >>> >>> The CSS Color spec, as rendered in Firefox, says: >>> "Note: Multi-word keywords in CSS usually separate their component words >>> with hyphens. current- >>> color doesn’t, because ..." >>> https://drafts.csswg.org/css-color/#ref-for-valdef-color-currentcolor-9 >>> >>> The hyphen in "current-color" seems unfortunate since the note is >>> trying to explain why that particular word doesn't have a hyphen... >>> >>> (hint: the element has 'hyphens:auto') >> >> >> Ahahahahaha, that's great. I'll set hyphens:none on some of the link >> types. > > > Alternately, we should probably be using <code> around all of the property > and value names. Well, I fixed default.css and Bikeshed's stylesheet. That won't fix any published specs, unless we start putting Bikeshed-isms into base.css, but at least the draft server and any future TR specs will work correctly. ~TJ
Received on Friday, 8 April 2016 18:20:01 UTC