101156 - "evaluate" should look like default button

Status: RESOLVED EXPIRED

(SeaMonkey :: UI Design, defect)

Description

[Bradley Hart]

In the JavaScript console, the "evaluate" button should look like the default 
button for that window. It behaves like the default button (responds to 
hitting "enter" or "return" in the window). Patch coming soon.

mpt, any objections?

Comment 1

[Bradley Hart]

Attachment: patch

Comment 2

[[e-mail] (gone - use [e-mail] instead)]

r=[e-mail] (assuming Robert is cool with this).

Comment 3

[Robert Ginda]

js console != js debugger

Comment 4

[Bradley Hart]

It looks like "Evaluate" is no longer a standard button, which is a result of 
some chrome changes. Marking INVALID.

Comment 5

[sairuh (rarely reading bugmail)]

mass verification of Invalid bugs: to find all bugspam pertaining to this,
set your search string to "MagaritaLuisaChascarilloAvoidsInvalidBugs".

if you think this particular bug is *still* an open issue, please make sure of
the following before reopening:

a. where relevant, do check that it's actually still a problem with ***recent
trunk builds*** on the all appropriate platform[s]

b. provide clear, compelling reasons why this bug should be considered a valid one.

Comment 6

[Matthew T (active 1999-2002)]

Yes ma'am.

(a) Reproduced on build 2002040508, Mac OS 9.2.
(b) It looks extremely ugly.

Reopening.

Comment 7

[Paul Chen]

Reassigning to default owner

Comment 8

[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 9

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420