Downvoted, understandably perhaps, but nearly every time I see this sort of bug it's because someone has copy/pasted something from MS Word instead of using whatever native client input method was provided (usually a textarea or input field). Yes, blame the rendering script for not encoding properly, but I suspect this was Boehner's team copy/pasting from some internal MS Word doc. Cheap shot - they also likely copy/paste screenshots in to Word and mail those around too, instead of just mailing the actual graphic file. :)
Cheap shot - they also likely copy/paste screenshots in to Word and mail those around too, instead of just mailing the actual graphic file. :)
When I was in consulting doing software integration work, few things infuriated me more than client "bug reports" arriving in the form of an email containing a 15 megabyte MS Word doc with a bunch of un-annotated screenshots.
I really hope Google someday opens up the awesome bug report/screencap feature in Google+, that lets you highlight part of the screen and redact sensitive parts.
I almost wouldn't mind, except the screenshots are inevitably shrunk down so as to be unreadable.
In OSX, the cmd-shift-4 (and 3) keystroke which screenshots right in to a file are near life-transforming. Snap, drag the file into an email, and it's done. I'm sure there are utilities in Windows which do this, but having it built in is great - no apps to start or install.
Be glad if you've not worked on a project where problem reports can take the form of a blurry, badly contrasted cell phone camera snapshot of the kernel oops that's partially scrolled off the user's screen. :)
NO ONE DOES THAT ON WINDOWS OUTSIDE OF TECH GEEKS. EVERYONE pastes in to MS Word, then emails that document.
That said, from a geek standpoint, I still prefer having the raw image file that I snapped in a folder someplace so I can refer to it later without having to go through sent emails, but that's just a personal preference.
Actually the "send feedback" link in Google+ does exactly that: asking you to highlight parts of the page where the error occurs and then obscure any sensitive info.
