I know, as a Web developer, you automatically assume that your awesome Ajaxy Web-service lovin’ application is better than anything else ever devised in the history of mankind. Ergo, it’s impossible that you would think that a user would use something outside of your browser to perform a function that you have specifically coded into your application with all the deft, loving care you could between 4:10 and 4:30am the morning the application was scheduled to go live.
I mean, a user who is accustomed to the CTRL+P keystroke to print something, what a backward rube!
Say, for example, you need a Bing map to the Cambridge Hyatt.
Here’s that map on the computer screen:
Now, CTRL+P and:
Gee, that’s handy of them to tell me in a bit of text that I wasn’t doing it right, but here’s a thought: you’re not doing it right.
You need to account for things the user can do to your site with the browser. Even if it’s just a little text marring your beautiful screen layout that says, “To print, use the icon we provided because we suck.”
Bonus points to the person who can identify the other defect with the printed map.