Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

본 사이트는 여러분의 사용자 경험을 개선하기 위해 유지 보수를 진행하는 동안 기능이 제한됩니다. 도움말로 문제가 해결되지 않고 질문을 하고 싶다면 Twitter의 @FirefoxSupport 및 Reddit의 /r/firefox 채널을 활용하세요.

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

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

  • 3 답장
  • 14 이 문제를 만남
  • 12 보기
  • 최종 답변자: 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.