React: Keyboard Event Handlers All 'Null'

前端 未结 4 1681
南方客
南方客 2021-01-30 16:27

I\'m unable to get any of the React SyntheticKeyboardEvent handlers to register anything except null for the event properties.

I\'ve isolated t

相关标签:
4条回答
  • 2021-01-30 16:39

    As Riccardo Galli points out correctly, the log object is already garbage collected at the time you access it in the console.

    The solution I use is to just log a clone of the object, so it won't be garbage collected. Cloning can be done in a lot of ways, but since I use lodash, I log like this :

      handleKeyDown: function(e) {
          console.log(_.cloneDeep(e)));
        }
    
    0 讨论(0)
  • 2021-01-30 16:53

    BinaryMuse provided the answer on IRC. Turns out it's just a quirk; you can't read the properties directly from SyntheticKeyboardEvent -- you need to specify the properties from the handler:

    handleKeyUp: function(e) {
     console.log(e.type, e.which, e.timeStamp);
    },
    

    http://jsfiddle.net/BinaryMuse/B98Ar/

    0 讨论(0)
  • 2021-01-30 16:55

    console.log() is aynchronous and by the time it access the event React already garbage collected it (it reuses the event for performance reasons).

    For debugging purposes, the simplest thing to do is to tell React to not discard that event

    e.persist() // NOTE: don't forget to remove it post debug
    console.log(e)
    

    I can't find an API documentation, the method is at least documented in the sources https://github.com/facebook/react/blob/c78464f/src/renderers/shared/stack/event/SyntheticEvent.js#L155

    0 讨论(0)
  • 2021-01-30 16:55

    You can also extract the underlying (original) browser event from the Synthetic*Event wrapper via the nativeEvent property. E.g.,

    handleKeyDown: function(e) {
      console.log('keyDown:event', e.nativeEvent);
    },
    

    (Just as with @Riccardo's note about e.persist(), it's unclear how you're supposed to know this without reading the React.js source code.)

    0 讨论(0)
提交回复
热议问题