[BUG]: Extension not working until the review is not formally started

[toverux]

Impact

Hinder: It obstructs me to do what I want

Description

Since a recent update (I think since you added Slack support), Conventional Commits does not work for me as long as the review process isn't started, i.e. you didn't post a first comment and clicked "Start a review".
After that you can edit the comment and the badges editor shows up without issues.

Same behavior with all other extensions disabled or the Slack button integration.

Same behavior in Chrome and Firefox.

Unsollicited and unrelated advice: I also find the Slack button a bit intrusive, I want to keep it, it's just a little big and perhaps not at best place. Otherwise, love the extension!

Steps To Reproduce

Capture.video.du.2025-09-04.14-41-37.mp4

Additional Information

No response

[CescHolly]

Hi @toverux, apologies for the delay. I've been trying to reproduce this in Chrome and Firefox and can't get it to happen.

When the message pop-up appears there's a MutationObserver that should pick it up and inject the buttons. There's also a timeout that checks every second (as a fallback), that's why sometimes it loads with a small delay.

I will try to find any possible reasons for this issue you're experiencing and get back to you (although it's going to be hard to check wether they're really fixed without reproducing the issue).

Could you please confirm:

• You are using GitHub (from the video: in the "new experience" Files Changed page preview, with "Split" diffs view).
• You're using Google Chrome (although you said it also happens to you in Firefox).
• This happens both when:
  • You load directly into a "Files changed" page from a new chrome tab (e.g. here)
  • You navigate to a "Files changed" page from a different GitHub page (e.g. first here, then open the PR and switch to the tab)
• This happens with the first pop-up comment textarea of the page, both when:
  • There were no other existing comments.
  • There were some other existing comments (from the video: I assume not).

Thanks again for your patience and glad you enjoy the extension ;))

[toverux]

Hi!

I forgot to post here, but the issue solved itself a few weeks ago!

It lasted for a while though, it was not just a little random and temporary malfunction.

I have no idea what could have provoked it in the first place, since I should have carefully tested it in isolation with no other extensions, and yes it was in two unrelated browsers and two different machines 🤷‍♂️

At least it's solved!