[X] My Assistant

Thanks, it works now, but there is a problem with the style of the buttons in MPV.
PS: Image Size Settings - Horizontal is set to 700px[/img]

Working as intended, it would have to limit the width of the images (or at least the bars) if we wanted to prevent overlaps in all cases.

And is it possible to add a scroll bar for MPV?

You can add it with a user style if you want it, but it won't be added by default or as an official option as it would probably break stuff if people move it around too quickly.

Working as intended, it would have to limit the width of the images (or at least the bars) if we wanted to prevent overlaps in all cases.

It seems I didn’t express myself clearly. What I mean is:
If I set a maximum width for the image, then neither the image nor the button should exceed the set value, just like before (main site, the second part in the image).
But now, the button exceeds the width of the image, making it harder to click (test site, the first part in the image).

It seems I didn’t express myself clearly. What I mean is:
If I set a maximum width for the image, then neither the image nor the button should exceed the set value, just like before (main site, the second part in the image).
But now, the button exceeds the width of the image, making it harder to click (test site, the first part in the image).

Oh, right. Yeah, that's a trivial fix, try it now.

Oh, right. Yeah, that's a trivial fix, try it now.

It works now, thanks!

Wanted to ask if the change of options for displaying thumbnails rows in gallery from 4/10/20/40 to 4/8/20/40 was intentional?
Is it reasonable to ask for option for having 10 rows again?

Wanted to ask if the change of options for displaying thumbnails rows in gallery from 4/10/20/40 to 4/8/20/40 was intentional?

This is intentional, because we'll have two different tilesets that are 20 and 40 thumbs each, so all thumbnails-per-page options must be divisible by 20 and 40.

PS: If people want to OCD about "then why not 25 and 50 thumbs per tileset" because they really want 100 per page, it's because for 200x thumbs, while 25 is only divisible by 5, 20 is divisible by 2, 4 and 5. Which means that with 25 per page, there will be a row of leftover thumbs at all narrower screen widths, while with 20, we avoid that with all widths except those that result in 3 thumbs per row. Similarly for 100x thumbs, while 40 is divisible by 2, 4, 5, 8 and 10, 50 is only divisible by 2, 5 and 10. (Disregarding numbers above 5 for 200x thumbs and 10 for 100x thumbs since we never go above that number of thumbs per row).

This is intentional, because we'll have two different tilesets that are 20 and 40 thumbs each, so all thumbnails-per-page options must be divisible by 20 and 40.

PS: If people want to OCD about "then why not 25 and 50 thumbs per tileset" because they really want 100 per page, it's because for 200x thumbs, while 25 is only divisible by 5, 20 is divisible by 2, 4 and 5. Which means that with 25 per page, there will be a row of leftover thumbs at all narrower screen widths, while with 20, we avoid that with all widths except those that result in 3 thumbs per row. Similarly for 100x thumbs, while 40 is divisible by 2, 4, 5, 8 and 10, 50 is only divisible by 2, 5 and 10. (Disregarding numbers above 5 for 200x thumbs and 10 for 100x thumbs since we never go above that number of thumbs per row).

Understandable, Have a Nice Day (IMG:[invalid] style_emoticons/default/smile.gif)