Closed
Bug 745569
Opened 13 years ago
Closed 6 years ago
keyup issue fires only on number press
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
Future
People
(Reporter: mathewkbentley, Unassigned)
Details
(Keywords: regressionwindow-wanted)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_3) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.151 Safari/535.19
Steps to reproduce:
opening this html in firefox mobile 10.0.3 I only see alert boxes when entering a number, sometimes only if its at the beginning of the textfield:
<html>
<head>
<title>keyup bug in mobile FF</title>
</head>
<body>
<input type="text" id="itemName" value=""/>
<script>
document.getElementById('itemName').onkeyup = function (event) {
alert('im here');
alert(event.keyCode);
alert(event.which);
}
</script>
</body>
</html>
Actual results:
onkeyup does not execute for any keypresses except numbers
Expected results:
onkeyup should execute even if the key pressed is not a number
|
Reporter | |
Comment 1•13 years ago
|
||
I actually found this writing a simple jquery mobile app using the standard $('#itemName').bind( 'keyup', function(){}) and noticed only mobile ff was affected. Managed to reproduce with the simple example above, which works in the other major browsers (chrome, android default browser, dolphin, opera mobile, safari, safari mobile, desktop ff 10.0.2 etc.).
|
||
Comment 2•13 years ago
|
||
Hmmm, this doesn't seem likely to be a JS engine bug to me. If the key is not a number, do you get any kind of error messages, as if the JS is running incorrectly, or is it just that the JS function doesn't run at all. If the latter, sounds like an event bug.
Keywords: regressionwindow-wanted
|
|
Reporter | |
Comment 3•13 years ago
|
||
The event does not fire at all unless the press is a number. The code in the report is live @ http://randomchooser.xtreemhost.com/test/test-ff.html for easier testing. I'd like to snoop around in the event handling, but can only find out how to remotely debug in mobile ff and have not invested in configuring that.
|
|
||
Comment 4•13 years ago
|
||
(In reply to mathewkbentley from comment #3)
> The event does not fire at all unless the press is a number. The code in the
> report is live @ http://randomchooser.xtreemhost.com/test/test-ff.html for
> easier testing. I'd like to snoop around in the event handling, but can only
> find out how to remotely debug in mobile ff and have not invested in
> configuring that.
Thanks for the clarification. It's also useful to know that setting up remote debug for mobile is a big barrier.
Looks like a DOM event thing to me, so sending it over there.
Assignee: general → nobody
Component: JavaScript Engine → DOM: Events
QA Contact: general → events
|
||
Updated•13 years ago
|
Component: DOM: Events → Event Handling
|
|
Reporter | |
Comment 5•13 years ago
|
||
I've confirmed this is reproducible in ff mobile beta (12.0) as well.
|
|
||
Updated•13 years ago
|
Component: Event Handling → General
Product: Core → Fennec
QA Contact: events → general
Target Milestone: --- → Future
Version: 10 Branch → Trunk
|
||
Comment 6•6 years ago
|
||
Closing all opened bug in a graveyard component
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•