Ok I looked into this information a bit. The FF "input" event should
only be raised for keys that change the input. Tab usually moves to
the next control. Enter seems to depend, on INPUT elements I guess it
causes submit by default. For these cases, there would be no "input"
event.
Just to be clear, the difference I am looking for is between these two
cases:
1) fresh FF+firebug, when enter/tab works, event stream on an INPUT
and TEXTAREA element when tab/enter/'a' are pressed.
2) same but after the keys quite working.
No difference in the event streams?
John.
On Apr 3, 4:49 pm, "Morgan Allen" <
morganral...@gmail.com> wrote:
> The difference is the input event does not occur for tab and enter, while it
> does for every other key.
>
> pressing 'a'
> keydown charCode=0, keyCode=65
> keypress charCode=97, keyCode=0
> input
> keyup charCode=0, keyCode=65
>
> pressing 'tab'
> keydown charCode=0, keyCode=9
> keypress charCode=0, keyCode=9
> keyup charCode=0, keyCode=9
>
> I also mentioned in my last email that shift-enter will submit form, but it
> also throws and error if logging is turned on.
>
> panel is null console.js (line 44)
>
> Hope this gives some sort of starting point. Having a quick look, the only
> reference I seem to find to input event is on line 1191 in dom.js
>
> On Thu, Apr 3, 2008 at 12:27 PM, John J Barton <
johnjbar...@johnjbarton.com>
> wrote:
>
>
>
>
>
> > Ok here is a suggestion.
>
> > While the enter is working bring up Firebug on a page where you think
> > the problem could occur in future (eg form filling or maybe google's
> > interface to this group).
>
> > Inspect the page, find the textarea that you will be using. On Firebug
> > HTML panel,right click on the textarea, select LogEvents.
>
> > Enter some text, esp enter and tab keys, to see what happens.
>
> > Now go on and wait for the problem.
>
> > Now with the problem, repeat: Do you see enter and tab events or
> > not???
>
> > John.
>
> --
http://morglog.alleycatracing.com