Skip to content
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

Laggy lookup on Chrome/Edge for file with a massive <pre> block #1423

Closed
Tracked by #1465
birtles opened this issue Nov 9, 2023 · 1 comment · Fixed by #1481
Closed
Tracked by #1465

Laggy lookup on Chrome/Edge for file with a massive <pre> block #1423

birtles opened this issue Nov 9, 2023 · 1 comment · Fixed by #1481

Comments

@birtles
Copy link
Member

birtles commented Nov 9, 2023

Reported by email, for a given ~300Kb HTML file that consists nearly entirely of one very large <pre> block, 10ten's lookup speed is noticeably laggy in Chrome/Edge. It's fine in Firefox.

I'm still checking if I'm allowed to link the file here since it contains song lyrics which may be copyright.

@birtles birtles mentioned this issue Nov 27, 2023
11 tasks
@birtles
Copy link
Member Author

birtles commented Nov 29, 2023

Not sure when I'll get to this but just for my notes, when I briefly looked at this, I wondered if we could store the last mouse position without converting it to page coordinates (and only convert it when we need it). If so that should reduce CPU usage when the add-on is not activated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant