[Bug]: scrolling problem [linux/appimage]

linuxgirl22 commented 2 years ago

Guidelines

[X] I have encountered this bug in the latest release of FreeTube.
[X] I have searched the issue tracker for a bug report that matches the one I want to file, without success.
[X] I have searched the documentation for information that matches the description of the bug I want to file, without success.

Describe the bug

Thank you for this new release. :-) Noticeably running a lot faster! Have an issue with scrolling; scrolls but stops at video title ... when continue, only right column moves, and clicking on 'comments' isn't possible until reach the bottom of the right column. When click on 'comments', comments open at the bottom, and need to scroll up to start reading. Just opened console, and the scrolling issue isn't there while console is open. A video width error shows; I have the text zoomed up, to help with comments size, so videos are larger too, showing 2 per line. (Have channel names showing text beside, too.)

Expected Behavior

Had been using one of the nightlies, I think from about 3-4 weeks ago, and no issue at all with scrolling as expected, by placing mouse anywhere, and can get directly to comments.

Issue Labels

feature stopped working

FreeTube Version

17.0

Operating System Version

MX Linux 21, 5.10.0-13-amd64

Installation Method

.AppImage

Primary API used

Invidious API

Last Known Working FreeTube Version (If Any)

FreeTube-0.16.0-nightly-1645.AppImage

Additional Information

Dragging screenshot in isn't working, but the error part about width:

Uncaught TypeError: Cannot read properties of null (reading 'videoWidth' at o.checkAspectRatio ... includes various refs to renderer.js:2

Nightly Build

[ ] I have encountered this bug in the latest nightly build.

linuxgirl22 commented 2 years ago

Hi :-) Wondering what to do about this bot thing marking thread as stale and pending closed; not keen to keep commenting to keep an active bug thread alive, if that's what the dumb thing is saying ... yes, not keen on all these bots etc, lol, and also prefer not to be on github. I've done a comment on this occasion, but all I can add regarding feedback is that still on Freetube 0.16.0 as scrolling is great in that but not working in 0.17.0. If another bot reminder to comment or close comes up, will just stick with Freetube 0.16.0 and thanks that it's possible to use that.

efb4f5ff-1298-471a-8973-3d47447115dc commented 2 years ago

Dont worry ill remove the label when the issue is valid no need to comment. If i dont and its the 6th day or something like that feel free to comment

linuxgirl22 commented 2 years ago

Thanks @efb4f5ff-1298-471a-8973-3d47447115dc. Can see 'stale' label removed, but can also see bug removed from 'To assign' ... no plans to fix broken accessibility features? or it's going into another queue? Really don't like the bot stuff etc, but didn't expect bug report possibly closed when said that, lol. Did report for anyone else needing to use larger text setting also, so fingers crossed it's not being closed, or closed because new features block it being fixed.

efb4f5ff-1298-471a-8973-3d47447115dc commented 2 years ago

Thanks @efb4f5ff-1298-471a-8973-3d47447115dc. Can see 'stale' label removed, but can also see bug removed from 'To assign' ... no plans to fix broken accessibility features?

This is definitely a bug of the workflow. I have created a bug report on their repo.

Really don't like the bot stuff etc, but didn't expect bug report possibly closed when said that, lol. Did report for anyone else needing to use larger text setting also, so fingers crossed it's not being closed, or closed because new features block it being fixed.

I can assure u that nothing will be closed or blocked automatically by bots. I understand why u dont like the automation stuff but it is necessary for us now that we keep growing. With the stale workflow we can evaluate if an bug report/feature request is really valid when its going stale. This will help us to get a healthy backlog and not get a enormous backlog like some other repos have.

linuxgirl22 commented 2 years ago

Thanks for assurances regarding bugs not being auto-closed/blocked; appreciate it.

The 'stale' auto-labelling unfortunately caused more work and confusion, in auto-threatening removal, forcing posting on github, and also in removing the bug from the project board ... and I'd thought it was a human, Preston, had done that removal, which wasn't great. It should be clear whether a human or a bot is doing something.

Am more put off from reporting even a show-stopping bug now, due to automation, but you've been very responsive and helpful about it, which I really appreciate. In closing, thanks for reporting to 'stale', and hopefully the scrolling bug can be re-added and work out okay.

linuxgirl22 commented 2 years ago

Just got an email update from #2704 ... thanks for continued efforts about fixing issues; much appreciate.

absidue commented 2 years ago

It should be clear whether a human or a bot is doing something.

Unfortunately due to GitHub limitations some actions have to be done by actual user accounts, as the default github bot account doesn't have enough permissions, so they need to be automated with an actual user account as well.

https://github.com/alex-page/github-project-automation-plus#personal-access-token

You will need a personal access token to send events from your issues and pull requests.

efb4f5ff-1298-471a-8973-3d47447115dc commented 2 years ago

@linuxgirl22 is it maybe possible for u to make a screen recording of the old and the new behavior?

linuxgirl22 commented 2 years ago

Hi and thanks for message. I've done two little recordings, one of 0.16 (working) and one of 0.18 (scrolling issue).

v0.16/working comments

https://user-images.githubusercontent.com/35760727/199937406-e1e6aec5-079d-4091-b877-4cde0bbdf2a9.mp4

v0.18/scroll issue

https://user-images.githubusercontent.com/35760727/199938807-b5ae9f24-a0ef-4653-b456-7b908c098a71.mp4

ramsaimanjunadh commented 2 years ago

Hi can i check the details by the given links.

On Fri, Nov 4, 2022 at 2:21 AM linuxgirl22 @.***> wrote:

Hi and thanks for message. I've done two little recordings, one of 0.16 (working) and one of 0.18 (scrolling issue).

https://user-images.githubusercontent.com/35760727/199937406-e1e6aec5-079d-4091-b877-4cde0bbdf2a9.mp4

Having a problem getting the second video down from 11.5 mb to under 10, but back soon.

— Reply to this email directly, view it on GitHub https://github.com/FreeTubeApp/FreeTube/issues/2436#issuecomment-1303161088, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXFV55FGSWNAQMO5T32B3N3WGTIQ3ANCNFSM55GL3JEQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

linuxgirl22 commented 2 years ago

Hi, sorry but I'm not sure what you're asking ... I was able to get the video downsized; using a locked down browser that doesn't play the videos, and was showing them as 'corrupt', but downloading one of them to check (the one in your attached text) resulted in it playing fine. Both should be okay and viewable in less locked down browsers or through download.

linuxgirl22 commented 1 year ago

Hello, I've got the email yet again saying "This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days."