Styles won't toggle when on a page

[Freezard]

Description

1. About a week ago the styles stopped working in real-time. For example if I have a style applied and deactivate it, the style will be removed, but when I activate it again nothing will happen. Deactivate toggle seems to work fine but never activate.
2. Reloading a page with the style checked will reapply it but if I try to toggle then the problem still exists. Reloading the extension will make everything work normal for a while, but it breaks after some time (couple hours?).
3. I tried to set Style cache duration to -1 and Instant inject mode on but it didn't help.

System Information

• OS: Windows 11
• Browser: Edge 131.0.2903.146 (64-bit)
• Stylus Version: 2.3.5 (from Chrome store)

Tested on Firefox 134 and didn't get the same issue.

[tophf]

Until the fixed version is published, clearing the cache by reloading the extension seems to work:

1. set Style cache duration to -1 in the options
2. right-click the Stylus icon -> Reload

[tophf]

I guess it may be caused by webpage caching on back/forward navigation, at least this is the only way I found so far to reproduce the bug. If you found a different scenario please walk me through it step by step.

[Freezard]

Will check tomorrow

[tophf]

Try also the nightly build, it fixes the problem I mentioned.

[Freezard]

It was working when I left the PC and when coming back a few hours later it was just broken (styles were still applied and working, but as soon as I untoggled them and toggled back they didn't get re-applied). And that was with Style cache duration -1 and not pressing back/forward on the pages. Tested nightly and I got the same problem. Firefox is still working fine.

[tophf]

In that case I need an exact sequence of steps I can perform to replicate the problem...

[tophf]

Also, when trying the nightly, make sure you disable the main Stylus extension and reload the tab(s).

[Trit34]

I have a similar issue since versions 2.x on Vivaldi (Chromium-based), as well on Windows (11 23H2) as on Arch Linux: if I enable styles, they apply. But if I disable them (let’s say, a style that darken a page a bit when it would be too bright), the style still applies on the previously visited specific URLs, despite being toggled off (and the browser closed, or the computer turned off). No matter I set the cache duration to -1, 0 or 30, it still happens and i have to manually toggle it on, then off, for the style stop applies for the current opened tabs (but if I click on a link to go to another URL, it can aply again despite being still turned off).

Some captures:

As you can see, “Global - Pseudo Brightness Control” style is off, yet it is active on a Mastodon page (and stays active whether I reload the tab or Stylus).

Each time the extension is updated, I believe this bug is fixed (not happened after updating to 2.3.5), but today, it was back…

[tophf]

Well, without an exact sequence of actions I don't know how to fix the bug, assuming it still exists in the nightly builds.

[Trit34]

Well, without an exact sequence of actions I don't know how to fix the bug, assuming it still exists in the nightly builds.

A way to check it out:

1. Enable a style in Stylus style manager or pop-up.
2. Browse some sites (YouTube, Discord, etc.) for some time (minutes, hours?).
3. Close tabs.
4. Go back to Stylus manager and disable the style.
5. Open again the previously opened tabs: they would still be “stylized” when they should not anymore.

[tophf]

Nah, I can't wait for hours, but I've just been able to replicate it on one site. Damn.

[tophf]

I wonder if it's caused by the "Instant inject" option, which I haven't tested much recently...

[Freezard]

In that case I need an exact sequence of steps I can perform to replicate the problem...

I will record my desktop and see if I can trigger the bug manually. Because right now I can't think of any specific actions leading to it other than it randomly happening after some time.

[tophf]

I can see the bug here now. Seems to occur randomly when using the same steps, which makes it hard to debug, but it's a start.