Skip to content

[FIX]: Content Script performance issues #2

Description

@RianaAzad
  • MutationObserver is constantly firing and rescanning the entire page
  • getTextNodes() scans the entire DOM tree every time
  • No debouncing or throttling for DOM changes
  • Regex patterns are being executed on every text node repeatedly
  • Large amount of DOM manipulation without optimization

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingdocumentationImprovements or additions to documentationenhancementNew feature or request

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions