- From: Brian Manthos <brianman@microsoft.com>
- Date: Sun, 14 Aug 2011 19:51:37 +0000
- To: Tab Atkins Jr. <jackalmage@gmail.com>, Sylvain Galineau <sylvaing@microsoft.com>
- CC: fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
Even if a page author has "designed the page with printing in mind", the user might still disagree and want to opt out of printing the images anyway. From an paid-for application perspective, user choice is king. From a content-author perspective, author choice is king. This isn't a new conflict, and I'm sure it will be going for a while. Another example: ad blockers. -Brian > -----Original Message----- > From: Tab Atkins Jr. [mailto:jackalmage@gmail.com] > Sent: Sunday, August 14, 2011 10:22 AM > To: Sylvain Galineau > Cc: Brian Manthos; fantasai; www-style@w3.org > Subject: Re: background-print > > 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. > > ~TJ
Received on Sunday, 14 August 2011 19:52:13 UTC