Currently, about:support "Copy all to clipboard" feature serializes the data displayed in a vertically sparse way, which makes it unfeasible for copy+pasting into bug report comments, emails, etc. Steps to "reproduce": 1. Go to about:support; 2. Press the "Copy all to clipboard" button; 3. Paste clipboard contents into a simple text editor (for example, Windows Notepad); 4. Paste clipboard into a rich text editor (for example, Microsoft Word). Expected results: 1. I'd expect the text-only version (from step 3) to be a little more "friendly"; 2. I'd expect the rich text version (from step 4) to be a little more "clean". Proposal is to: 1. Add less indenting in each entry; 2. Combine table cells into information tuples in the form "key: value"; 3. Treat the "Profile Directory" entry differently so that either it is suppressed (as there's no value in outputting "Open Containing Folder" in a text output) or actually output the directory as text during export (for example, "Profile Directory: C:\Users\MyUsername\... 4. Remove trailing space currently added all titles ("Application Basics ", etc.) and entries (all of "Application Basics", like "Name ", "Version ", etc.) 5. Maybe also consider expanding/suppressing "Enabled Plugins" and "Build Configuration" in the simple text clipboard version, as links aren't useful in a text-only output (I'm not sure if there's infrastructure for this). Current output is something like: Application Basics Name Firefox Version 4.0b7pre Proposed output would be something like: Application Basics Name: Firefox Version: 4.0b7pre For an example take a look at bug 594025 comment 30, where I have manually reformatted (part of) the output automatically generated.
I would also like Copy all to clipboard to output your current profile directory's path (your #3), but that won't be implemented; from bug 658186, "we don't want users accidentally giving away their OS username or profile nonce every time they paste from about:support."
Thanks for the proposal. There's an older bug about improving the output, so I'm going to dupe this one to that one, but I'll copy your proposal there.
(In reply to Drew Willcoxon :adw from comment #2) [...] > so I'm going to dupe this one to that one, but I'll copy your proposal there. Thanks for including my proposal there and not simply marking as duplicate, as many do. ;-)