non uniform thumbnail quality

[foxjaw]

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

0.25.2

Steps to reproduce the bug

NOTE: This is not related to #1782
Compare thumbnail quality of search results page with that of feed, playlists, channel pages, etc.

Expected behavior

All thumbnails should have unform quality

Actual behavior

Results page thumbnails are high quality than those of the rest of the pages elsewhere.

Screenshots/Screen recordings

THUMBNAILS IN THE FEED

THUMBNAILS IN THE CHANNELS

Logs

No response

Affected Android/Custom ROM version

No response

Affected device model

No response

Additional information

Thumbnail quality in feed, playlists, as well as channel page, look very bad compared to the thumbnail quality in search results.

I'm not saying to increase the quality. Just expecting the uniform behaviour everywhere. i.e, same quality everywhere, whether it's low or high, I don't care.

[foxjaw]

My old account (ask low) was sh@d0w b@nn3d by g!thub (caz I broke oauth agreements). This issue existed before, & was open (#10462).
Can you mention which MR fixed this ? Do you remember asking sameen that this bug is not related to setting image quality ? & I replied that I didn't ignore the template & searched for thumbnail, & asked to clean up the issue titles after closing them...

[ShareASmile]

Can you mention which MR fixed this ?

See #10062
which is included in v0.26.0 RC
#10471

[opusforlife2]

Oh, that's freaky. All your issues from the previous account are gone? That's... potentially very painful for any orgs containing issues/PRs/discussions opened by users who are later shadow-banned.

And damn, I was thinking of your previous issue when closing this as a duplicate.

Anyway, in the normal course, we could have opened this back up, but in this case, the feature is already added and just needs to be released. Sameen has linked the RC above.

[foxjaw]

Don't worry btw. It's just a sh@d0w b@n. As I can access all those issues from my side. I've reopened only those which were also open before.
Yes. This is indeed duplicate (of the issues that were gone). Feel free to close them when completed.

Can you mention which MR fixed this ?

See #10062 which is included in v0.26.0 RC #10471

Tq. Will try the debug version 0.26.0.