[Nighly] Toggling fullscreen causes "clear queue" prompt

[kubo6472]

Checklist

• I am able to reproduce the bug with the latest version given here: CLICK THIS LINK.
• I made sure that there are no existing issues - open or closed - which I could contribute my information to.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected version

Build 1031 of nighly

Steps to reproduce the bug

0. Turn this on

1. Open any video 2. Click to toggle fullscreen 3. Observe prompt to clear queue ### Expected behavior

No prompt, it's only fullscreen

Actual behavior

I see a prompt

Screenshots/Screen recordings

https://imgur.com/a/fRDopqM

This is reproduced with tubular, but I see the same behaviour with nighly newpipe

Logs

No response

Affected Android/Custom ROM version

No response

Affected device model

No response

Additional information

Regression probably caused by this PR merge #12044
Build 1030 is free of this bug
Build 1031 has this bug

[ShareASmile]

Please avoid using third-party websites to upload images when github supports them showing directly.

[kubo6472]

Showed me failed to upload like three times. If I could I would.

[dev-victoria]

This Issue already exists with Version 27.7

I wanted to enable it to avoid accidentally clicking on a suggested video, which immediately replaces the current queue.
Unfortunately it does not do that. If it is supposed to, something went wrong somewhere.

About Git Uploads

Showed me failed to upload like three times. If I could I would.

It likely was over 8Mb in size. I compress my stuff with ffmpeg.

Your video(prob. compressed by imgur):

r3bP4Jm.mp4

[Stypox]

According to git bisect, the incriminating commit is a7a7dc5, which is unfortunately quite big. Let me try to find out the problem.

[Stypox]

@kubo6472 and the others: thanks for reporting this before it goes into an official release! Could you test if #12416 fixes the issue?

[kubo6472]

@Stypox I do see it is fixed.