Skip to content

Conversation

@Geluchat
Copy link

Hello,

Support for Manifest V2 dropped in my Chrome version. I use this extension on a daily basis, so I just vibe-coded a quick patch to make it work with Manifest V3.

It's not great coding, but it works. Feel free to use it!

Best regards,
Geluchat.

@gregxsunday
Copy link

You're the man!

@Zeetaz
Copy link

Zeetaz commented Jul 14, 2025

Hello 👋

I've been playing around with several different V3 approaches - most inject too "slow" in V3 which causes a kind of race condition. This happens here as well, there are multiple async steps causing timing gaps where listeners can register before the tracker is active.

So, this version works well for catching dynamically loaded listeners but it will miss early listeners that gets added during page load. This seems to be solvable by executing immediately at document_start using "world":"MAIN" in Manifest V3 and should catch everything (I think?).

I made a little fork over here --> Manifest V3 Tracker

It has a test file there as well, seems to work fine. I haven't tried it a whole lot, but it seems to solve the issues I observed over here so I thought I might as well share it. 👍

It is by no means great coding (AI-slop mostly), but it could be another option until frans or someone with more experience than me feel like doing a proper re-write.

Cheers!
//Zettergren

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.

4 participants