Am 19.08.2011 13:39, schrieb Derrell Lipman:
On Fri, Aug 19, 2011 at 05:42, Christian Hagendorn
<[email protected] <mailto:[email protected]>>
wrote:
Hi Derrell,
thanks, I tested your example on Windows7 with IE9, FF6, Opera
11.5, Safari 5.1 and Chrome 13.
Your described issue occurs with all my tested browser, so it is
not a browser issue. :(
I found a workaround to get the value. The first trick is to call
a blur on the input field. This works for all browsers, but not
for Opera. Opera needs a timeout :(
Thanks, Christian. I'll add the bug report a little later.
Unfortunately, this is not a general solution. It's fine with a form
that contains only a single input field. This is a general problems
for all of my forms, though, including those with many input fields.
Do I need to call a blur on each and every input field? I don't know
of any way to determine quickly which input field is focused, in order
to call only its blur (although I could, I suppose, loop through all
input fields, looking for the focused one, and call its blur).
I would have thought that ok.focus() would cause a blur on the
previously-focused field...???
Derrell
Hi Derrell,
you are right the solution is not generally. I tried the FocusHandler to
get the current focused widget and it seems to me that this works:
var focusedWidget =
qx.ui.core.FocusHandler.getInstance().getFocusedWidget();
focusedWidget.getContentElement().getDomElement().blur();
Yes, that's right. The focus call on the ok button should blur the last
focused element?! (I Check this)
Cheers,
Chris
------------------------------------------------------------------------------
Get a FREE DOWNLOAD! and learn more about uberSVN rich system,
user administration capabilities and model configuration. Take
the hassle out of deploying and managing Subversion and the
tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
