You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On YouTube, fixing the option to force show/hide community posts on foldables/tablets. Forcing tablet layout on/off could be good too.
Those two options already exists in revanced but does nothing on a foldable/tablet since tablet layout is forced by the system.
Motivation
Currently on YouTube, on my OnePlus Open (so a foldable) the tablet mode is forced on by the system. The toggle tablet layout does nothing on those type of systems. So community posts are off whatever you do. I love to have the most information possible centralized in one app and community posts contributes to that (makes me avoid X/Twitter for exemple). Having them back on foldables/tablets would be huge and even more useful because you have the screen size to back it up !
Acknowledgements
I have checked all open and closed feature requests and this is not a duplicate
I have chosen an appropriate title.
All requested information has been provided properly.
The text was updated successfully, but these errors were encountered:
Feature description
On YouTube, fixing the option to force show/hide community posts on foldables/tablets. Forcing tablet layout on/off could be good too.
Those two options already exists in revanced but does nothing on a foldable/tablet since tablet layout is forced by the system.
Motivation
Currently on YouTube, on my OnePlus Open (so a foldable) the tablet mode is forced on by the system. The toggle tablet layout does nothing on those type of systems. So community posts are off whatever you do. I love to have the most information possible centralized in one app and community posts contributes to that (makes me avoid X/Twitter for exemple). Having them back on foldables/tablets would be huge and even more useful because you have the screen size to back it up !
Acknowledgements
The text was updated successfully, but these errors were encountered: