Skip to main content

Bug Tracker

Side navigation

#8780 closed bug (invalid)

Opened April 05, 2011 11:55PM UTC

Closed April 09, 2011 04:28PM UTC

events, preventDefault

Reported by: PatrickS Owned by: PatrickS
Priority: undecided Milestone:
Component: event Version: 1.5.2
Keywords: Cc:
Blocked by: Blocking:

Hi to the bug tracking team,

Trying to debug $(document).onkeypress() handler, I found a way to make my script working as expected... yupee! but finalizing / cleaning the source file, I mentioned that I wrote "e..preventDefault()" (yes, two points). I thought first that it was a language feature I ignored, like "/" in Unix path root! Correction -> it stopped working! Back to "..": it worked! Too strange, try with Opera and you guess the result. So ?  Do I have to send a bug report to Mozilla ?

Finally, I always had difficulties with events handlers... Now I have doubts on Firefoxe.

Mozilla/5.0 (X11; U; Linux i686 (x86_64); fr; rv: Gecko/20110319


Mozilla/5.0 (X11; Linux i686 on x86_64; rv:2.0) Gecko/20100101 Firefox/4.0

I was working first with jQuery 1.4.4. then passed to version 1.5.2


Thanks for the nice job you've done.


Attachments (0)
Change History (5)

Changed April 06, 2011 12:56AM UTC by timmywil comment:1

owner: → PatrickS
status: newpending

Please provide a test case on and explain your issue in plain English or some language we might be able to translate. onkeypress is keypress in jQuery and e..preventDefault is invalid javascript syntax.

Changed April 07, 2011 02:50AM UTC by PatrickS comment:2

status: pendingnew

Replying to [comment:1 tinywil]:

in plain English

Je crois qu'il aurait été bien plus convenable de dire que mon explication est incompréhensible. Mais bon: la bonne éducation n'est probablement pas anglo-saxonne.

or some language we might be able to translate.

Voilà qui est fait.

En conclusion, j'accepte volontiers vos remerciements pour mon apport. Vous comprendrez, si vous avez cette possibilité, que je n'irai rien déposer sur jsFiddle.

Changed April 07, 2011 02:04PM UTC by timmywil comment:3

status: newpending

Yes I understand and I didn't mean to be inappropriate. Incomprehensible is a better word to use. More information would be very helpful as we cannot understand what the issue is for this ticket. A test case on would clear things up for us. Thank you again!

Changed April 09, 2011 02:16AM UTC by anonymous comment:4

See Bugzilla@Mozilla – Bug 648696

Changed April 09, 2011 04:28PM UTC by rwaldron comment:5

component: unfiledevent
resolution: → invalid
status: pendingclosed

This is not a jQuery bug; It's a valid error triggered by Firefox's E4X implementation.

reduced test case: