Opened 6 years ago

Closed 4 years ago

#1027 closed task (wontfix)

More convenient next/previous page buttons

Reported by: DISABLED Owned by: zzz
Priority: trivial Milestone:
Component: apps/i2psnark Version: 0.9.7.1
Keywords: usability Cc:
Parent Tickets: Sensitive: no

Description

If you want to skip many pages in I2PSnark it becomes tedious if the next/previous buttons move each time. This way it's hard to skip pages in a row and it wouldn't take big effort to expand the buttons a bit (or have them on a fixed location).

Subtickets

Change History (4)

comment:1 Changed 6 years ago by zzz

I don't understand. The buttons move? They are in the same place for me, at the top of the middle column.

comment:2 in reply to:  1 Changed 6 years ago by DISABLED

Replying to zzz:

I don't understand. The buttons move? They are in the same place for me, at the top of the middle column.

They seem to be - but they're only close to the same place of the page. They move a bit most of the time. If you got many pages you're going to notice it when skipping pages - it's tedious if you quickly want to jump to a page or just glance over the torrent section instead having to "manually" navigate & click the button each time. They seem to be just centered. Maybe you're not using the default design ? It's not a major problem but it would be truly useful for anyone having a few pages of torrents if they'd be made a little bigger so one can click the same spot for quick skips.

comment:3 Changed 5 years ago by str4d

Keywords: usability added; page buttons i2psnark removed
Milestone: 0.9.8

comment:4 Changed 4 years ago by zzz

Resolution: wontfix
Status: newclosed

I don't have the CSS skills to lock these in place without bad side effects. The column widths may change as you go through the pages, which may cause the button position to move slightly.

I could lock the columns to a fixed width, but that would prevent the browser from picking the best layout for the current browser width and font size, which would be a cure worse than the OP.

While I understand the issue and sympathize, I don't see how to fix it.

Closing wontfix.

Note: See TracTickets for help on using tickets.