Build: Add jtr-based tests in GitHub Actions, migrate to ESLint flat config #247
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes:
.editorconfig
&.gitattributes
files.gitignore
to include more patterns from jQuery CoreI'm considering further changes for the future, like:
We could then release such a smaller version as 4.0.0. I just wanted to add some real CI on real browsers first.
I know we discussed potentially deprecating this plugin and just telling people to use the
wheel
event directly. The problem is thewheel
event may report deltas in pixels, lines or pages. Chrome may report pixels or pages, Firefox can report all three depending on input devices. This plugin can be useful to get some pixel-based normalization; as long as browsers don't provide that out of the box, I see some value in this plugin. There are some discussions about always exposing pixels, perhaps in addition to other modes, in w3c/uievents#181, but so far the discussion has stalled.That said, I had a look at jQuery UI and it only cares about the wheel direction and only in one place so I don't see why UI needs to depend on this plugin anymore.