[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Make "First name", "Company name", ... and "Country" fields optional

From: Davi Leal
Subject: Re: Make "First name", "Company name", ... and "Country" fields optional too
Date: Mon, 14 May 2007 11:41:43 +0200 (CEST)

Victor Engmark wrote:
> Davi Leal wrote:
> > About the police to hide/show not-required fields, I propose:
> >
> >   * If it is the first time the user fill that form,
> >     hide by default non-required fields.  For example, for
> >     registration of Person, Company, etc., the first time
> >     you fill your Qualifications.  About the JobOffer I am not sure.
> In general, I think it's only critical that we hide optional fields when
> registering. The reason is to turn away as few people as possible at that
> crucial point (many people are unwilling to register if they have to provide
> a lot of information).


All the non required fields are hidden at the register operation.  The
entities will able to fill the non-required fields after completing the
registration process.

> Another place where hiding things can be useful is at
> the job search page, for similar reasons - New users shouldn't have to use
> fields they are not comfortable with.


I will take note of this at the "Job filtering and search" task adding a
reference to this email.

> On the other hand, those who are already registered want to be sure that
> their profiles, job offers, and searches are as accurate as possible, in
> order to get the best match. That could be easier to achieve by showing all
> the fields in those forms.

OK,  but maybe this contradict your previous proposal, some weeks ago,
about removing the JavaScript requirement at the JobOffer and
Qualifications forms, and at the same time _be able to hide_ the not
required fields?.

I suppose we will think more about it when we be ready to realize the
"Remove the JavaScript requirement" task.

> I also think it's a good idea to save the users' "view" of different forms
> in a cookie, and perhaps include it in their settings. What do you think?

The user "view" state or view data?
Do you mean the user view settings?

I think that if it is needed, using a cookie is the way to go.
What are you thinking to save in that cookie or cookies?

P.S.: I hope be ready soon to help on the transition to DIV.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]