Frank,
Sorry for the latency. I was actually using 'onkeypress' and not
'onkeyup'. I tried using 'onkeyup' and that works. Try using
'onkeypress' and see if you can reproduce it.
If so, hopefully something can be done to handle 'onkeypress'
consistently across all platforms. Does JS even ha
see wicketKeyCode() func in wicket.js that might be of some help.-IgorOn 10/20/06, Frank Bille <[EMAIL PROTECTED]
> wrote:Do you have some example code for that? I can't reproduce it (FF1.5),
when I'm doing something like this:FrankOn 10/20/06, Frank Bille <[EMAIL PROTECTED]> wrote:
> On 10/20/
Do you have some example code for that? I can't reproduce it (FF1.5),
when I'm doing something like this:
Frank
On 10/20/06, Frank Bille <[EMAIL PROTECTED]> wrote:
> On 10/20/06, Matthew P. Tilchen <[EMAIL PROTECTED]> wrote:
> >
> > Unfortunately the mozilla-based browsers do not
> > includ
On 10/20/06, Matthew P. Tilchen <[EMAIL PROTECTED]> wrote:
Unfortunately the mozilla-based browsers do notinclude the keyCode attribute on the event, it always comes throughas 0 for any key. The other browsers do include the correct unicodevalue.
Hmm, do you mean in terms of onkey* on tag? I'll tr
Thanks again Frank. That was extremely helpful. For the record, all
the browsers I tested do fire the event off the body object (Mozilla-
based, Safari, IE). Unfortunately the mozilla-based browsers do not
include the keyCode attribute on the event, it always comes through
as 0 for any key.
Wicket doesn't have something like that but you can do it yourself. Take a look at this to get an idea:http://www.nabble.com/CTRL%2Bclick-tf2047972.html#a5640400
FrankOn 10/19/06, Matthew P. Tilchen <[EMAIL PROTECTED]> wrote:
Thanks for the help Frank. The changes you mentioned solved myproblem. I
Thanks for the help Frank. The changes you mentioned solved my
problem. I was operating under the fallacious assumption that the
Page object was attached to the tag.
Now, regarding the following:
"getBodyContainer().getBodyContainer() returns the WebMarkupContainer
which corresponds with the
getBodyContainer().getBodyContainer() returns the WebMarkupContainer
which corresponds with the tag. (Though I don't know how good
the support is for having javascript events on the tag in the
different browsers)
Frank
On 10/19/06, Frank Bille <[EMAIL PROTECTED]> wrote:
> You need to attach the
You need to attach the event to a tag in the markup. Since the Page
component is not directly attached to any tag then you can't use that.
Instead use:
public class Index extends WebPage
{
public Index()
{
super();
final Label testLabel = new Label(this, "message", "Hello
Greetings,
I am not certain as to whether this post will end up being a bug
report or a feature request but hopefully one of you may have some
advice.
Ultimately I am trying to invoke ajax calls as a result of capturing
"onkeypress" events fired by the document object. I have successfully
10 matches
Mail list logo
