🐞If using the Force Autoplay Off function, playback is not possible.

[duk6046]

Concise Description

Playback becomes impossible.

Browser/s

Chrome

Other Browser:

No response

'Steps to reproduce' - Which of our features is required for the bug to happen?

Force Autoplay Off

Since when?

Today

Does the bug still happen when you log out of YouTube?

• Yes
• No

..No? Then please paste your yt.config_.EXPERIMENT_FLAGS. Twice (With the error & Without)

No response

Are any errors or related log-messages shown in the Browser-Console? (F12)

No response

Tested as the only active extension? (incognito mode or another browser users):

• Yes
• No

Expected preferred behavior:

No response

ImprovedTube Version

4.1090

Your Settings (From the Extension's ⋮-Hamburger menu > Settings > Backup & reset > Export settings)

No response

Your YouTube-Document

No response

OS / Device:

win11

[ImprovedTube]

hi and thanks! @duk6046 i think the reason is (was) "Undo the new side bar"? #2520

Sending the fix to the stores now.
Meanwhile we can test https://github.com/code-for-charity/ImprovedTube-for-YouTube/archive/refs/heads/master.zip

[duk6046]

hi and thanks! @duk6046 i think the reason is (was) "Undo the new side bar"? #2520

Sending the fix to the stores now. Meanwhile we can test https://github.com/code-for-charity/ImprovedTube-for-YouTube/archive/refs/heads/master.zip

I'm not using 'Undo the new sidebar' feature, existing opened tabs cannot be play, only works newly opened tabs, tested on v4.1091.

[duk6046]

it happens often, there are randomness, this may have been the case from the beginning...

[ImprovedTube]

hi @duk6046!
#2511 (comment) @GusTheAnt said, the "fit to window" player-button could cause this.
The button was also fixed thanks to @SabalM! #2516

[duk6046]

hi @duk6046! #2511 (comment) @GusTheAnt said, the "fit to window" player-button could cause this. The button was also fixed thanks to @SabalM! #2516

It works, turn off that option and working well. thanks

[ImprovedTube]

It should be fixed in v4.1091+ anyway though, isn't?

(And while it's strange when things change "non-gracefully" (let alone backwards compatibly) (=when that world standards change, so that code, which was fine becomes not only outdated but also a "bug"),
luckily we can wrap every feature in a try { } catch { } , so this could have been prevented.

[duk6046]

It should be fixed in v4.1091+ anyway though, isn't?

Umm.. it wasn't resolved on v4.1093, still conflict with 'fit to window' funtion.