You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2015/03/08 01:50:38 UTC
[jira] [Created] (INFRA-9250) Self serve does not allow empty
attributes to be set
Sebb created INFRA-9250:
---------------------------
Summary: Self serve does not allow empty attributes to be set
Key: INFRA-9250
URL: https://issues.apache.org/jira/browse/INFRA-9250
Project: Infrastructure
Issue Type: Bug
Components: Selfserve
Reporter: Sebb
The self-serve app does not allow empty attributes to be set up.
This is because of lines 258/259 in [1], where the field is set to disabled if the attribute is not present in the values for the current record.
A simple fix is to remove the lines.
However, this then causes a problem, because empty fields are pre-populated with the value "<not present>", which will get written to the attribute if the user does not clear the fields first. This would be tedious and error-prone.
Dropping the "<not present>" value does not work either, because the field is currently only rendered if there is a value for it.
The changedetails.html template needs to show at least one field for every supported attribute whether it has an actual value or not.
For writable fields, one could use a field placeholder attribute [2] to show the "<not present>" text. This would also be suitable for read-only fields.
Whatever approach is taken, there needs to be a way to test the changes.
Is there a test installation of the SelfServe app that can be used to check that the page renders OK?
[1] https://svn.apache.org/repos/infra/infrastructure/selfserve/trunk/lib/selfserve/__init__.py
[2] http://www.w3schools.com/tags/att_input_placeholder.asp
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)