hmmm after doing some testing... using the blur event isn't
working .... if an item is clicked (i.e. a selection is made), the
blur event of the textbox is getting fired first, which "cancels" the
panel and falls back to the initial value of the textbox....so
basically... the "cancelPanel" function gets called all the time and
"acceptValue" never gets called...

adding a click event to the body kinda yields the same result...


On Oct 13, 1:43 pm, SilverTab <[EMAIL PROTECTED]> wrote:
> Thanks to both of you for the suggestions!...
>
> I added both the "esc" keydown event and the blur event to hide the
> panel...
>
> On Oct 13, 12:20 pm, "Guillermo Rauch" <[EMAIL PROTECTED]> wrote:
>
> > On Mon, Oct 13, 2008 at 2:15 PM, nutron <[EMAIL PROTECTED]> wrote:
> > > I'd like to suggest that you implement some way to "cancel" out of the
> > > interface. I would do the following:
> > >  - Add an event watcher for the document body for clicks. If the user
> > > clicks somewhere other than the elements in your picker, hide it.
>
> > I like the focus/blur approach myself
>
> > >  - Add a similar event that watches keystrokes; if they hit the escape 
> > > key,
> > > hide it.
>
> > Agreed (add optional blur())
>
> > >  - Consider finding some way to add a tiny "x" in the interface that will
> > > close it (for people who don't try either of the above)
>
> > Agreed (add optional blur())
>
> > > Was thinking about the name of the class and for some reason, the phrase
> > > "HoverFlow" keeps coming to mind. Maybe because it sounds like "CoverFlow"
> > > which is another popular interface meme. Just thought I'd share. I don't
> > > really have a preference about the name.
>
> > Haha, amazing name.
>
> > --
> > Guillermo Rauchhttp://devthought.com

Reply via email to