Skip to content

#6293 Use batch inject for content scripts - #6294

Closed
sosnovsky wants to merge 2 commits into
masterfrom
6293-batch-inject-content-scripts
Closed

sosnovsky wants to merge 2 commits into
masterfrom
6293-batch-inject-content-scripts

Conversation

@sosnovsky

Copy link
Copy Markdown
Collaborator

This PR uses batch inject for content scripts injection, instead of multiple calls

close #6293


Tests (delete all except exactly one):

  • Does not need tests (refactor only, docs or internal changes)

To be filled by reviewers

I have reviewed that this PR... (tick whichever items you personally focused on during this review):

  • addresses the issue it closes (if any)
  • code is readable and understandable
  • is accompanied with tests, or tests are not needed
  • is free of vulnerabilities
  • is documented clearly and usefully, or doesn't need documentation

@sosnovsky
sosnovsky requested a review from martgil September 22, 2026 08:18
@martgil

martgil commented Sep 22, 2026

Copy link
Copy Markdown
Collaborator

Hi @sosnovsky - there's nothing to merge here now as it was already in the master branch (from an already merged #6296).

@sosnovsky

Copy link
Copy Markdown
Collaborator Author

Oh, you're right - I copied changes from this PR to test #6296, and since it was merged earlier - this one can be closed.

@sosnovsky sosnovsky closed this Sep 22, 2026
@martgil
martgil deleted the 6293-batch-inject-content-scripts branch September 22, 2026 12:43
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 this pull request may close these issues.

Use executeScript({files: [...]}) instead of multiple executeScript()

2 participants