hapershield hapershield schrieb:
> Hi Sebastian,
>I am using 0.7 alpha1 version,It has the focus issues for text
> field in case of firefox(text fields are not getting focus,if tab key is
> pressed).These have been fixed in 0.7.1 version.But i should use the
> alpha version only as lot o
Hi all,
Can any one please let me know the focus issues fixed in 0.7.1.
On 9/19/07, hapershield hapershield <[EMAIL PROTECTED]> wrote:
>
> Hi Sebastian,
>I am using 0.7 alpha1 version,It has the focus issues for text
> field in case of firefox(text fields are not getting focus,if tab key i
Hi Sebastian,
I am using 0.7 alpha1 version,It has the focus issues for text field
in case of firefox(text fields are not getting focus,if tab key is
pressed).These have been fixed in 0.7.1 version.But i should use the alpha
version only as lot of work was done with alpha version api.Can you
Hi Sebastian,
Thank you for the explanation. You are right, it works. I did
the mistake at another place, so the function was not called,
but doing test, I could not find the entry I had expected, so
I was confused, how it should work.
Maria
Am Mi, 19.09.2007, 16:54, schrieb Sebastian Werner:
>
Hi Maria,
the focus handling is controlled by the FocusManager. This managers
"hacks" itself into the tab key sequence and overwrite the browsers
default behavior. This is needed because some browser do not support
tabIndex on all elements and also because otherwise there would not be a
chance
Hi,
I have a question concerning the Tab Index of a widget.
I thought this is an equivalent to the setting TabIndex of an input
control in html, if it used with an form widget. When looking inside the
source code of the widget, i could see that it does not manipulate this
property, but I don't kn
