Bug 636735 - Dashboard - Message Portlet: Edit mode is overly-aggressive in disallowing blank fields.
Summary: Dashboard - Message Portlet: Edit mode is overly-aggressive in disallowing bl...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.0.0
Hardware: All
OS: Linux
low
medium vote
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Corey Welton
URL:
Whiteboard:
Depends On:
Blocks: rhq4 jon30-dashboard
TreeView+ depends on / blocked
 
Reported: 2010-09-23 04:45 UTC by Corey Welton
Modified: 2011-05-24 01:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Corey Welton 2010-09-23 04:45:15 UTC
Description of problem:
When trying to edit a field in in the Message portlet, the GUI gets grumpy if you try to delete all the content in order to replace it.

Version-Release number of selected component (if applicable):


How reproducible:
Every time.

Steps to Reproduce:
1.  Add a Message portlet to your dashboard
2.  Click the "edit" button and enter the value "foobar" in the field; save.
3.  After returning to dashboard view, click the edit button again.
4.  Attempt to backspace over the text you've entered, or Ctrl-X the whole thing.
  
Actual results:

UI is validating before you've actually submitted anything, and thus won't let you leave that field blank.  You cannot simply remove the text before putting something else in the box- this is rejected.

Expected results:

Something a bit more user-friendly.

Additional info:

Comment 1 John Mazzitelli 2011-02-17 19:21:49 UTC
smartgwt seems to have this working now

Comment 2 Corey Welton 2011-03-02 21:51:11 UTC
Verified.

Comment 3 Corey Welton 2011-05-24 01:11:54 UTC
Bookkeeping - closing bug - fixed in recent release.

Comment 4 Corey Welton 2011-05-24 01:11:56 UTC
Bookkeeping - closing bug - fixed in recent release.


Note You need to log in before you can comment on or make changes to this bug.