logo

New Response

« Return to the blog entry

You are replying to:

  1. On a more serious note, a small caveat.

    I have sites that create reports based on lookups such as this.

    The problem with allowing users at the open field (a lot of mine are not that computer savvy) is that they can type anything in there. The field passes validation 'cos it's not empty.

    About 2 months ago, I changed all my type ahead from your namepicker widget to the Ext type ahead facility (Similar to the field you have demo'd here) which I was told "users find more intuitive" by people who supposedly know about these things.

    Mayhem ensued as my users (bless them) typed any old thing and pressed create report - 404 errors filled my logs

    Never count on your users to grasp the concept of type ahead when they can just type what they want. Life isn't that kind!

    So last week I converted all of my apps back to using your name picker widget, and hiding the open field.

    The beauty of your NPWidget is that it doesn't allow people to apply free text to a specific search, and I'm sticking with it. - My server's happier too.

    A small point I know, but one I think is worth considering when deploying.

Your Comments

Name:
E-mail:
(optional)
Website:
(optional)
Comment: