ICEfaces
  1. ICEfaces
  2. ICE-10183

icecore:defaultAction does not capture all keyboard events in some browsers

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 4.0.BETA
          • Fix Version/s: 4.0, EE-3.3.0.GA_P06
          • Component/s: None
          • Labels:
            None
          • Environment:
            Chrome, IE 8/9/10

            Description

            icecore:defaultAction does not capture all keyboard events in some browsers such as _Esc_ and _F..._ keys.

              Activity

              Descending order - Click to sort in ascending order
              Hide
              Permalink
              Arturo Zambrano added a comment -

              r52745: backported fix to the EE 3.3 maintenance branch

              Show
              Arturo Zambrano added a comment - r52745: backported fix to the EE 3.3 maintenance branch
              Hide
              Permalink
              Ken Fyten added a comment -

              I wonder if the jsEventListener should consume the event after it processes it? This might not stop the browser from doing what it wants though, in which case we should just use different keys for the example/demo and avoid any that have native browser functions.

              Show
              Ken Fyten added a comment - I wonder if the jsEventListener should consume the event after it processes it? This might not stop the browser from doing what it wants though, in which case we should just use different keys for the example/demo and avoid any that have native browser functions.
              Hide
              Permalink
              Liana Munroe added a comment -

              Many of the keyboard events are now captured but when using some of them, the default browser action is also fired. For example, submitting with the F3 key works, but it also launches the browser's "Find" dialog. Submitting with the F2 key works, but it also launches the browser's "Help" dialog. These are just 2 examples of this occurring, there are more. Is this expected behaviour?

              Show
              Liana Munroe added a comment - Many of the keyboard events are now captured but when using some of them, the default browser action is also fired. For example, submitting with the F3 key works, but it also launches the browser's "Find" dialog. Submitting with the F2 key works, but it also launches the browser's "Help" dialog. These are just 2 examples of this occurring, there are more. Is this expected behaviour?
              Hide
              Permalink
              Mircea Toma added a comment -

              Register callback with onkeydown instead of onkeypress event to make sure all the keys are captured. Browsers like Chrome and IE will not fire keypress events for keys that are meant to control the browser.

              Show
              Mircea Toma added a comment - Register callback with onkeydown instead of onkeypress event to make sure all the keys are captured. Browsers like Chrome and IE will not fire keypress events for keys that are meant to control the browser.

                People

                • Assignee:
                  Mircea Toma
                  Reporter:
                  Mircea Toma
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: