[Cent Browser] Tampermonkey does not work at multilogin tabs

[dnknn]

	chrome://extensions/?id=dhdgffkkebhmkfjojejmpbldmpobfkfo

Screenshot from the Internet imageScreenshotLiveDemo

Then, just enter the incognitol mode and open the web page to test...

Expected Behavior

• • • ON☑ : Can work! (just like Violentmonkey)

Actual Behavior

• • • ON☑ : Can not work ..... (It is exactly the same as disabling Tampermonkey)

---

• Chromium: 80-86-90
• TM: All versions, at least the last 1 year.
• OS: Win10

[7nik]

TM 4.13 and TM Beta 4.14.6142, Chromium 91, KDE Manjaro. TM works, scripts run with no errors.

[dnknn]

TM 4.13 and TM Beta 4.14.6142, Chromium 91, KDE Manjaro. TM works, scripts run with no errors.

Thank you for your reminder, I tested and verified again and found that there is indeed no problem.

The problem appears in the fork browser of Chromium similar to this feature,

[dnknn]

But having said that, the function can be fixed/enhanced, I think it’s a problem with the API,
🗣: because Violentmonkey and Stylus , and any other extensions ,etc. they all work fine (Verified by comparison!)!.

So I think it’s a private bug of Tampermonkey

• This is the browser : 　　　　　http://centbrowser.com/history.html
  • Ctrl+M or right-click in the browser Tab, to open New multilogin tab
  • multilogin tab : Its essence is actually to use the browser’s incognitol API
    　

I open this issue, if the author does not want to support this issue, please close it directly.

[derjanb]

Tampermonkey gets no navigation or other events from multilogin tabs. 🤷

Not sure how they implemented this mode, but no new Tampermonkey background page is started, like it is done when a regular incognito tab is created.

Other extensions might work because they don't use split mode to secure potentially sensitive data of incognito mode tabs.

[derjanb]

I've posted a bug report at their forum: https://www.centbrowser.net/en/showthread.php?tid=4084

[derjanb]

Thanks for your feedback.
This is an old issue of multilogin tabs.
We need to fully refactor this feature to solve it.