Feedback:Required fields - Revision history

EnricoDaga: Text replace - ' token ' to ' taken '

2010-02-26T10:07:21Z

Text replace - ' token ' to ' taken '

Admin: Text replace - '|Author=User:' to '|Author='

2009-03-10T15:46:16Z

Text replace - '|Author=User:' to '|Author='

EnricoDaga at 09:27, 21 October 2008

2008-10-21T09:27:40Z

EnricoDaga at 15:35, 30 June 2008

2008-06-30T15:35:57Z

EnricoDaga at 15:35, 30 June 2008

2008-06-30T15:35:27Z

EnricoDaga at 10:07, 6 June 2008

2008-06-06T10:07:39Z

EnricoDaga at 10:07, 6 June 2008

2008-06-06T10:07:20Z

EnricoDaga at 10:06, 6 June 2008

2008-06-06T10:06:18Z

Admin at 09:54, 28 May 2008

2008-05-28T09:54:33Z

MariaPoveda: New page: {{TitleDescription Template |Title=Required fields |Description=It is a good practice in terms of designing web pages to indicate which fields are required with a * in all forms, for examp...

2008-05-26T09:19:55Z

New page: {{TitleDescription Template |Title=Required fields |Description=It is a good practice in terms of designing web pages to indicate which fields are required with a * in all forms, for examp...

New page

{{TitleDescription Template
|Title=Required fields
|Description=It is a good practice in terms of designing web pages to indicate which fields are required with a * in all forms, for example at Add Content OP Proposal Form. Besides, I proposed to change the error message when a user doesn’t fill a required field because sometimes it is not clear if the required field is that following or preceding the alert, for example when a users doesn’t fill the field “intend” in a proposed CP the message error appear between “intend” and “domain”.
}}
{{Feedback Template
|Author=User:MariaPoveda
|Priority=High
|Status=To be done
}}

@@ Line 11: / Line 11: @@
 |Answer=I agree with this issue. The way the systems manage the mandatory fields of the form is probably not the best solution.    Other problem with forms are the dimensions of the lists, of example for the fields like 'authors', above in this form... that could become too large when number of users would increase.
-This and others 'usability' problems are token in account, and we are dealing with for better solutions.  [[User:EnricoDaga|Enrico]]
+This and others 'usability' problems are taken in account, and we are dealing with for better solutions.  [[User:EnricoDaga|Enrico]]
 }}

@@ Line 4: / Line 4: @@
 }}
 {{Feedback Template
-|Author=User:MariaPoveda
+|Author=MariaPoveda
 |Priority=Low
 |Status=fixed

@@ Line 6: / Line 6: @@
 |Author=User:MariaPoveda
 |Priority=Low
-|Status=dealing with
+|Status=fixed
 }}
 {{Answer Template

@@ Line 9: / Line 9: @@
 }}
 {{Answer Template
-|Answer=I agree with this issue. The way the systems manage the mandatory fields of the form is probably not the best solution.    Other problem with forms are the dimensions of the lists, of example for the fields like 'authors', above in this form... that could become too large when number of users would increase. &#13;&#10;&#13;&#10;This and others 'usability' problems are token in account, and we are dealing with for better solutions.  &#91;&#91;User:EnricoDaga&#124;Enrico]]
+|Answer=I agree with this issue. The way the systems manage the mandatory fields of the form is probably not the best solution.    Other problem with forms are the dimensions of the lists, of example for the fields like 'authors', above in this form... that could become too large when number of users would increase.
 }}

@@ Line 9: / Line 9: @@
 }}
 {{Answer Template
-|Answer=I agree with this issue. The way the systems manage the mandatory fields of the form is probably not the best solution.    Other problem with forms are the dimensions of the lists, of example for the fields like 'authors', above in this form... that could become too large when number of users would increase.
+|Answer=I agree with this issue. The way the systems manage the mandatory fields of the form is probably not the best solution.    Other problem with forms are the dimensions of the lists, of example for the fields like 'authors', above in this form... that could become too large when number of users would increase. &#13;&#10;&#13;&#10;This and others 'usability' problems are token in account, and we are dealing with for better solutions.  &#91;&#91;User:EnricoDaga&#124;Enrico]]
-−
-This and others 'usability' problems are token in account, and we are dealing with for better solutions.  [[User:EnricoDaga|Enrico]]
 }}

@@ Line 1: / Line 1: @@
 {{TitleDescription Template
 |Title=Required fields
 |Description=It is a good practice in terms of designing web pages to indicate which fields are required with a * in all forms, for example at Add Content OP Proposal Form. Besides, I proposed to change the error message when a user doesn’t fill a required field because sometimes it is not clear if the required field is that following or preceding the alert, for example when a users doesn’t fill the field “intend” in a proposed CP the message error appear between “intend” and “domain”.
 }}
 {{Feedback Template
 |Author=User:MariaPoveda
 |Priority=High
-|Status=To be done
+|Status=dealing with
 }}