Skip to content

non-passive event listener bug #1166

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Atomic-Germ opened this issue Feb 25, 2025 · 0 comments
Open

non-passive event listener bug #1166

Atomic-Germ opened this issue Feb 25, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@Atomic-Germ
Copy link
Contributor

Atomic-Germ commented Feb 25, 2025

Describe the issue
Currently, if you run npm start and just leave it running with devtools turned on, you will see two issues. First, the known event.sender.send issue. Secondly, there's an issue that crops up after a while being idle:

[Violation] Added non-passive event listener to a scroll-blocking 'mousewheel' event. Consider marking event handler as 'passive' to make the page more responsive.

Screenshot
Image

To Reproduce
Steps to reproduce the behavior:

  1. npm start
  2. Click on 'view` and toggle devtools
  3. Switch between the calendar views
  4. See error

Expected behavior
The listeners should be passive. This not only deals with the problem but also can improve performance to some degree.

Environment

  • Node/npm version: 23.6.1 / 11.1.0
  • OS: MacOS 15.3.1
  • TTL version: main
@Atomic-Germ Atomic-Germ added the bug Something isn't working label Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant