![Firefox logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
Firefox 29 update does not recognize event "keypress" when pressing (intro) (keycode 13) over <select> element on form
Hi Mozilla friends, I have ome issues after the 29 Update: I develop surveys for quick data registration using html5 and jquery, before the Update the event keypress aplied to select elements was working fine (users register data using numeric keyboard and instead of tab they use enter key for navigate to the next field , the field can be an input or a select) I have a function that simulates a tab when a user press the enter key using keypress, but the event is not fired anymore with that key. I 'd like to know if it is a bug or a programmed update to Firefox.
PD: Thanks for al your efforts Mozilla!!!
Réiteach roghnaithe
I think I found it: Bug 935876 – <select> element shouldn't consume key events which don't cause any default action.
This bug is a fix to a fix so it's a little confusing, but the idea is to discard the keypress event for the Enter key because...
// If the select element is a dropdown style, Enter key should be // consumed everytime since Enter key may be pressed accidentally after // the dropdown is closed by Enter key press.
I'm not sure that really makes sense but there is so much history in that and the earlier bug that I can't follow all the arguments.
Read this answer in context 👍 1All Replies (3)
Yes, I have an old page with a function that does a similar thing and I see that change also.
I make a Fiddle for watching the events on the select: http://jsfiddle.net/rXDsW/
I can't think of a reason for this change, and didn't immediately see something in Bugzilla for it. But I am not very good at searching Bugzilla...
Réiteach Roghnaithe
I think I found it: Bug 935876 – <select> element shouldn't consume key events which don't cause any default action.
This bug is a fix to a fix so it's a little confusing, but the idea is to discard the keypress event for the Enter key because...
// If the select element is a dropdown style, Enter key should be // consumed everytime since Enter key may be pressed accidentally after // the dropdown is closed by Enter key press.
I'm not sure that really makes sense but there is so much history in that and the earlier bug that I can't follow all the arguments.
Hello jscher2000, well, I guess this is a tricky one issue, so I had changed the event by keydown, I've already tested and it works fine. Thanks for your very quick response.