Bug 112304 - [Dialogs] in cvs commit dialog return key not work
Summary: [Dialogs] in cvs commit dialog return key not work
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-12 05:16 EDT by apla CLA
Modified: 2019-09-06 16:07 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description apla CLA 2005-10-12 05:16:56 EDT 
when i fill cvs comment in cvs commit dialog, in eclipse 3.1M? return key acts
as clicking button "Finish". in later releases (3.1 and 3.2M2, at least) when i
press return key with filled comment, button "Finish" blinks, but nothing. when
comment is unfilled, pressing return key shows warning - " Please enter a commit
comment." and button "Finish" take disabled state.
Comment 1 Kim Horne CLA 2005-10-13 13:09:40 EDT 
The problem is that focus is in a multiline text field.  In this case, enter should just take you to the next 
line.  You should be able to dismiss the dialog via command-enter.
Comment 2 Kim Horne CLA 2005-10-13 13:09:59 EDT 
er, make that command-return
Comment 3 apla CLA 2005-10-17 05:47:45 EDT 
eclipse 3.2m2
1. nor command-return, nor command-enter not work. only control-enter. this wrong
2. finish button reflects (blinks on) any combination of
enter/return/command-enter/command-return, but nothing.
3. need to be fixed "Finish" disabled button state, as described in my previous
message.
Comment 4 Susan McCourt CLA 2007-07-02 19:41:05 EDT 
changing prio and status to conform to plat-ui bug guidelines
Comment 5 Susan McCourt CLA 2009-07-09 16:55:24 EDT 
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:07:00 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.