53480 - print function for Error Console

Status: RESOLVED WONTFIX

(Toolkit Graveyard :: Error Console, enhancement)

Description

[Mike Stockman]

There's no way to get any information out of the JavaScript Console. The
commands on the Edit menu (Cut, Copy) are dimmed and can't be selected, and
there's no print command on the File menu or anywhere else. Even a Save command
would be useful.

This came up because I wanted to print/copy/save a series of JS errors to show
the script's developer. I couldn't do it...

Comment 1

[Zach Lipton [:zach]]

confirming bug. This doesn't seem too hard to do. Severity to minor, this is 
not such a big deal.

Comment 2

[John Bandhauer]

mccabe or ben?

Comment 3

[Mike McCabe]

I can take this.  Help would be wonderful.

Comment 4

[Mike McCabe]

*** Bug 60534 has been marked as a duplicate of this bug. ***

Comment 5

[sairuh (rarely reading bugmail)]

*** Bug 46344 has been marked as a duplicate of this bug. ***

Comment 6

[sairuh (rarely reading bugmail)]

any possible status/milestone possibilities for this puppy?

Comment 7

[Jesse Ruderman]

I don't think the js console needs Cut or Paste, but Copy is important.

Comment 8

[Joe Hewitt (gone)]

A fix for the clipboard portion of this bug in the patch in bug 67647.

Comment 9

[Keyser Sose]

*** Bug 69880 has been marked as a duplicate of this bug. ***

Comment 10

[Jesse Ruderman]

From bug 69880: the js console should be multi-select to allow copying multiple 
items.  In that case, a Select All command should also be added to the Edit 
menu and to the context menu.  (Maybe that should be a separate bug, but either 
way, it depends on the last batch of changes to the js console going in (bug 
67647).)

Comment 11

[Mitchell Stoltz (not reading bugmail)]

cc'ing John Taylor. John, since you worked on the JS console in the past, would
you be interested in working on this?

Comment 12

[Joe Hewitt (gone)]

Clipboard functionality is implemented in the patch for bug 67647, so I'm
changing the summary to just include print.

Comment 13

[Jesse Ruderman]

Changing this to an enhancement, since it will be possible to print using a 
text editor once copying out of the javascript console works.

Comment 14

[Jesse Ruderman]

Oops, "js console should be multi-select" is bug 67603.

Comment 15

[Phil Schwartau]

Mass-reassigning mccabe's non-JS, non-Rhino bugs to jband (34 total). 

Would like to cc mccabe; but the mass-reassign page does not allow this. 
I'll leave it up to mccabe to decide if he wants to be cc'ed on these - 

Comment 16

[John Bandhauer]

reassign to hewitt (since he's actually done some work on the JS Console)

Comment 17

[Christopher Aillon (sabbatical, not receiving bugmail)]

*** Bug 100042 has been marked as a duplicate of this bug. ***

Comment 18

[Christopher Aillon (sabbatical, not receiving bugmail)]

*** Bug 121363 has been marked as a duplicate of this bug. ***

Comment 19

[Max Alekseyev]

*** Bug 121602 has been marked as a duplicate of this bug. ***

Comment 20

[Travis Chase]

*** Bug 35279 has been marked as a duplicate of this bug. ***

Comment 21

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 22

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 23

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 24

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 25

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 26

[Nochum Sossonko [:Natch]]

This is being moved out of Seamonkey and into Toolkit, please exclude it from the mass changes.

Comment 27

[Colby Russell :crussell (no longer Mozilla-ing)]

I'm taking the liberty of closing this, since it should have been closed somewhere around comment 12 when Copy was implemented, and the last 12 years of activity here is just bug churn.  No one's gonna implement printing for the Error Console.