Bug 760232 - [RFE] Put "save", "clear" etc. buttons in the edit div for textbox fields.
Summary: [RFE] Put "save", "clear" etc. buttons in the edit div for textbox fields.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
low vote
Target Milestone: Unspecified
Assignee: Mike McCune
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-05 16:55 UTC by Corey Welton
Modified: 2018-08-30 21:57 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-18 15:12:36 UTC
Target Upstream Version:


Attachments (Terms of Use)
mockup (64.28 KB, image/png)
2011-12-05 17:07 UTC, Corey Welton
no flags Details

Description Corey Welton 2011-12-05 16:55:07 UTC
Description of problem:

Text fields (vs, say, single line inputs) can be very long, and it would be nice to be able to save or clear the data from within edit mode in the field without scrolling down to the bottom to hit action buttons. Especially useful when people might have the tendency to click outside a textbox to scroll down a page, thus losing anything unsaved that they have pasted into the field.

The idea here would be to place secondary save/clear/etc. icons in the gray div that contains the edit button (the pencil/lines icon). These would only visible/enabled when edit mode is engaged. 

Again, this wouldn't work with single-line input fields, but it wouldn't be necessary there either, since there's not a lot of UI real estate taken up by these and the users wouldn't find themselves scrolling to access the action buttons.

I'll try to put together a screenshot/mockup to accompany this, as to provide a better illustration.

Comment 1 Corey Welton 2011-12-05 17:07:49 UTC
Created attachment 541023 [details]
mockup

Comment 7 Roxanne Hoover 2016-10-18 14:57:18 UTC
No, not standard patternfly.


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