I think there's a nomenclature issue here. If you have a button on the page that says...
*Print* The user clicking this will expect the page to print but will not be given the chance to preview the output before their print dialogue appears. *Print(er) Friendly* The user will click expecting to see a printer friendly version appear that they can then decide whether to print or copy/paste as detailed by previous respondents. The fact remains that the most elegant solution is to use a print CSS but perhaps we could combine the two button scenarios by using a combination (accepting that the copy/paste is '20 rather than 80'): 'Print simplified page' or (if button space isn't a problem) 'Print (our pages are printer friendly)' and variations thereof which would intend to inform the user that their action was going to print the page directly but that the version they saw would be printer friendly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=28529 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
