W3C home > Mailing lists > Public > www-style@w3.org > August 2011

RE: background-print

From: Sylvain Galineau <sylvaing@microsoft.com>
Date: Mon, 15 Aug 2011 14:40:53 +0000
To: Tab Atkins Jr. <jackalmage@gmail.com>
CC: Brian Manthos <brianman@microsoft.com>, fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <3C4041FF83E1E04A986B6DC50F01782931E075@TK5EX14MBXC296.redmond.corp.microsoft.com>

[Tab Atkins Jr.:]
> On Sat, Aug 13, 2011 at 11:31 PM, Sylvain Galineau
> <sylvaing@microsoft.com> wrote:
> > [Tab Atkins Jr.:]
> >> A property with a properly-broad name, like "printer-safe-colors",
> >> would allow the author to hint in that direction.
> >>
> >
> > Note that printing may not be the only motive for background
> > suppression and higher contrast. Accessibility settings on some
> > platforms also do this to view the content. High contrast is not just a
> printing issue.
> Keep in mind the intent of the property, though - it's meant to say "Hey,
> I know you normally suppress my backgrounds and mess with my colors when
> you print, but I've designed the page with printing in mind, so there's no
> need to do that here (unless the user still asks for it)."
> While I agree that there are other use-cases for UAs messing with colors,
> I don't think it's good to mix the "I've thought about printing"
> declaration with an "I've thought about contrast levels"
> declaration.

That's fair. And I shouldn't fool myself into the 'the name of its property 
will obviously define how it's used' corner anyway :)

Received on Monday, 15 August 2011 14:41:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:03 UTC