搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

Firefox 29 update does not recognize event "keypress" when pressing (intro) (keycode 13) over <select> element on form

  • 3 回覆
  • 14 有這個問題
  • 82 次檢視
  • 最近回覆由 cquispem

more options

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!!!

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!!!

被選擇的解決方法

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.

從原來的回覆中察看解決方案 👍 1

所有回覆 (3)

more options

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...

more options

選擇的解決方法

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.

more options

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.