8.1.1 revived the problem 🔴

[DAO8]

before 8.1.1 we fix the issue by console commands, but new update revived the problem, please fix this once and for all

[rkodey]

Hello @DAO8 - I'm trying to understand the sequence you're showing in that screen capture.

• Are you switching between several suspended tabs?
• And then is the Update banner displaying, and then disappearing on each tab once?
• What browser are you using, and operating system?

Thanks!

[rkodey]

And just to make sure...

• Can you open up Marvellous Suspended settings, and go to the About tab, and verify the version you're running?
• And the console fix you tried before doesn't work?
• What about restarting your browser?

Thanks again - this is very strange behavior you're seeing!

[neodon]

I'm experiencing the same issue for a while now (weeks?). It's not consistent - it seems to only happen after I am on active tabs for a while and then start switching to suspended tabs.

First it will flash the update banner for about half a second as I click through a few suspended tabs for the first time.

Then it will turn into very quick flashes for the first click on each suspended tab.

After the first click on each suspended tab, going back and forth it renders correctly, instantly.

Windows 10
Chrome 142.0.7444.136
Extension confirmed to be 8.1.1

Random thought: I wonder if there is some bug with Chromium's built-in memory saving features causing otherwise hidden content to be rendered incorrectly. Is there a chance the banner does render every time, but in the optimal case it is hidden immediately and not perceptible?

I tried various ways to debug the issue via dev tools and debug logs, but Chrome has nuked just about every possible way to inspect extensions now.

[neodon]

Looking at the code, I think it's plausible that a very slow render would cause the update banner to show before the JavaScript can set its display style to none.

MarvellousSuspender/src/js/suspended.js

Line 117 in 0f33f48

el.style.display = update ? 'block' : 'none';

I wonder if setting the default display style to be none would fix the issue, e.g. in suspended.html: <div id='tmsUpdateAvailable' style='display:none;'>

[rkodey]

Thanks for the details!
Yes, I was considering the "display none" on the last update... but since the last update fixed a much larger issue, I was hoping this whole problem would be solved. And we also have a recent PR that's essentially doing the same thing. So yes, I think that's the direction to go. I should be able to get this resolved over the weekend.

It does seem to be related to slow rendering - at least that's my best guess. I'll run a bunch of tests artificially making the render run slow and see if we can get this annoyance resolved.

[rkodey]

The v8.1.2 maint branch is in progress and should fix this issue. I just removed the link here just so it doesn't auto-close this issue, so we have time to test it out before confirming it's complete.