According to the usage in InputEvent specInputEvent.data should be nullable. (Link to the definition in UIEvent)
The reasons are:
InputEvent.data is not inherited from UIEvent, so it's OK to make it nullable;
InputEvent relies on the null check to tell JS which attribute they should use - data or dataTransfer;
We can't use data == "" in this case because:
There are other inputTypes (e.g. 'formatBold') that shouldn't have a data field, and having data == "" would make it confusing;
It's possible for an IME to fire an InputEvent with empty text, which should still be valid (Not 100% sure if any browser is actually doing this though)
@garykac
According to the usage in InputEvent spec
InputEvent.datashould be nullable. (Link to the definition in UIEvent)The reasons are:
InputEvent.datais not inherited fromUIEvent, so it's OK to make it nullable;InputEventrelies on the null check to tell JS which attribute they should use -dataordataTransfer;data == ""in this case because:inputTypes (e.g.'formatBold') that shouldn't have adatafield, and havingdata == ""would make it confusing;InputEventwith empty text, which should still be valid (Not 100% sure if any browser is actually doing this though)