4 Replies Latest reply on Jun 12, 2009 5:09 AM by Ilya Shaikovsky

    filterby event

    Jonathan Roberts Newbie

      I know this a little wacko.

      My users want filtering capability but they are keyboard centric users. So if I add filterEvent="onKeyUp" it filters however, they want to be able to tab through the filter input texts and not have table rerender everytime they hit tab.
      So I change to filterEvent="onChange". But they have a problem with how that works. If they put in a value and click a button without first tabbing out of the filter text box, (why would they even do that) two request are sent and I think they are stepping on each other and causing problems sometimes.

      Is there a way to get a hybrid of the two behaviors? Like set the event to onKeyUp except when that key is the Tab key? Or onKeyUp only when a change has been made?

      Thanks in advance for any help.