add an option to disable data mutation displaying

Open
#36 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
performance

Research direction

Start in firefox/chrome/content/firequery.js at line 683 and inspect the .eq call and surrounding data-mutation display flow. Determine where an option to disable this display belongs and how it should be exposed. Done means the option prevents the expensive display work while preserving the existing behavior when enabled; no test or entry point is named in the issue.

Written by the indexing model from the issue text.

Description

the .eq call on line https://github.com/binaryage/firequery/blob/master/firefox/chrome/content/firequery.js#L683 uses far too much CPU time if there is a lot of data attached to DOM nodes, this can be seen in the attached image:

firequery-profile

Dominant language
JavaScript
Stars
170
Forks
18
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from binaryage/firequery

All issues in binaryage/firequery

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.