Bug 789514 - [WebUI] leading and trailing spaces in 'description' textarea is not allowed
Summary: [WebUI] leading and trailing spaces in 'description' textarea is not allowed
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Martin Kosek
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-10 23:35 UTC by Yi Zhang
Modified: 2015-01-21 15:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-21 15:08:03 UTC
Target Upstream Version:

Attachments (Terms of Use)
there is one empty spaces after the word 'Update' (105.74 KB, image/png)
2012-02-10 23:35 UTC, Yi Zhang 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Yi Zhang 2012-02-10 23:35:36 UTC 
Created attachment 561009 [details]
there is one empty spaces after the word 'Update'

Description of problem:
Please check the screen shot for the error dialog.
My question is: do we really care about leading and trailing spaces in "description" ? This is annoying for customer.

Version-Release number of selected component (if applicable): IPA devel daily build
Comment 2 Dmitri Pal 2012-02-13 13:06:19 UTC 
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/2380
Comment 9 Martin Kosek 2015-01-21 15:08:03 UTC 
Thank you taking your time and submitting this request for Red Hat Enterprise Linux. Unfortunately, this bug was not given a priority and was deferred both in the upstream project and in Red Hat Enterprise Linux.

Given that we are unable to fulfill this request in following Red Hat Enterprise Linux releases, I am closing the Bugzilla as DEFERRED. To request that Red Hat re-considers the decision, please re-open the Bugzilla via appropriate support channels and provide additional business and/or technical details about its importance to you.

Note that you can still track this request or even contribute patches in the referred upstream Trac ticket.
Note You need to log in before you can comment on or make changes to this bug.