- From: Brian Manthos <brianman@microsoft.com>
- Date: Thu, 1 Dec 2011 18:46:27 +0000
- To: David Chambers <david.chambers.05@gmail.com>
- CC: Chris Nager <cnager@gmail.com>, "www-style@w3.org" <www-style@w3.org>
- Message-ID: <9710FCC2E88860489239BE0308AC5D170450C095@TK5EX14MBXC264.redmond.corp.microsoft.>
In IE5, “#12” was treated as the same as “#120” IIRC. Cases like “#1234” also have interesting treatment. So, compatibility is one concern. I don’t have an opinion on what’s sensible or not about that treatment. But I do take issue with saying “there’s only one way to intepret #mn” when we have at least one decacde-old public implementation that proves otherwise. -Brian From: David Chambers [mailto:david.chambers.05@gmail.com] Sent: Thursday, December 01, 2011 10:10 AM To: Brian Manthos Cc: Chris Nager; www-style@w3.org Subject: Re: [css] Proposal: making Shorthand Hex Colors even shorter (16 grayscale shades) Brian Manthos <brianman@microsoft.com<mailto:brianman@microsoft.com>> wrote: Given that “#rgb” expands within channels (#rrggbb), why should “#mn” expand across channels (#mnmnmn)? I don't see this as a problem. Since there's no sensible way to expand "#mn" within channels, why not have it expand in a different — importantly, obviously different — manner? David On 1 December 2011 03:55, Brian Manthos <brianman@microsoft.com<mailto:brianman@microsoft.com>> wrote: Given that “#rgb” expands within channels (#rrggbb), why should “#mn” expand across channels (#mnmnmn)? From: Chris Nager [mailto:cnager@gmail.com<mailto:cnager@gmail.com>] Sent: Tuesday, November 29, 2011 9:34 AM To: www-style@w3.org<mailto:www-style@w3.org> Subject: Re: [css] Proposal: making Shorthand Hex Colors even shorter (16 grayscale shades) Hey Markus, I completely agree. I sent a tweet out about this a while back: https://twitter.com/#!/ChrisNager/status/83651049558253568 @ChrisNager: "As far as color hexcodes go in #css, I've always thought if #0cf works for #00ccff, shouldn't #f work for #ffffff and #a1 work for #a1a1a1?" Cheers! Chris Nager cnager@gmail.com<mailto:cnager@gmail.com>
Received on Thursday, 1 December 2011 18:47:08 UTC