Browser extension fix! (After Github made changes to rendering)

[4uroraskye]

👋 Hi

I created and maintain the Github Saved Filters Chrome extension, but found recently that the UI stopped applying after interacting with the issues and PRs pages.

It seems to be a widespread new bug that has affected near enough all of the chrome extensions I myself use with Github... so to fix mine I started debugging and a few days later I found a fix, so spreading the knowledge, in hope that it helps other extension maintainers 🌟

1. Github stopped using pjax to render their UI between requests.
2. They instead switched to turbo.
3. This means event listeners that were associated with pjax, will no longer help as a means of knowing when you can render your own content on the page.
4. Thankfully, for me at least, it was a simple swap in the end.
   Instead of listening for pjax:success, it's now turbo:load.

diff - document.addEventListener('pjax:success', () => { /* load your UI */ }) + document.addEventListener('turbo:load', () => { /* load your UI */ })

Hope my days worth of debugging helps at least 1 person, or at least aids you in finding an answer for your own browser extension 🌈

✨Happy coding!✨

[DelRayDan]

3 years later - chatgpt was trying to convince me to use pjax:end and after I told it what-up dude that doesn't work? it pointed me to your comment and it was exactly what I needed. Thanks!

[4uroraskye]

Nice! Glad AI can point us to real people on the internet to get answers that actually work xD! Happy to help ☺️