Works: Next and Previous Chapter links should skip users past the work meta to reduce scrolling

Description

The problem

When using the Next Chapter and Previous Chapter links to navigate between chapters of a work, a user must scroll past the site header and the work meta (i.e. the box at the top of the page) to get to the main content. The meta can sometimes be very long.

The proposed solution

Make the Next and Previous Chapter links skip past the user past the header and site meta, like so: https://test.archiveofourown.org/works/83081/chapters/111888#workskin

This could be accomplished with an anchor, as demonstrated, or via some other means.

Activity

Show:
Sarken
August 14, 2018, 5:53 PM

The behavior is the same with the Next/Previous buttons at the top of the work. It feels a little awkward/unexpected there, particularly if you don’t scroll at all before clicking it – it’s hard to articulate why, but basically if you’re navigating within the same site and you don’t scroll before clicking a link, you don’t really expect a drastic change when the next page loads – but I don’t think that’s really a problem.

Runt
August 18, 2018, 10:42 PM

used work https://test.archiveofourown.org/works/989821/chapters/1953274

Buttons on top and bottom work as expected, bypassing the metadata box

DreamSea
August 19, 2018, 1:06 AM

If further work is done, possibly have it such that bottom navigation scrolls (user probably had to scroll to get to that point + reading delay) where as top doesn’t scroll (perhaps user is paging through the chapters one by one instead of using chapter index dropdown)?

mumble
August 25, 2018, 6:31 AM

I agree that it’s a nice little time-saver when using the bottom row of buttons; a bit weird when navigating from the very top of the page to the next. However, unless we get support tickets about this, nothing super problematic, like Sarken said.

Lady Oscar
August 27, 2018, 12:12 AM

I agree that this feels weird when used from the top buttons, and is very sub-optimal when one wants to flip quickly through chapters (for example, to try to figure out which chapter one last read). On the other hand, it solves the problem I've always had where I hit "Next Chapter" on the first chapter, then quickly click again to get to chapter 3...and am back at chapter 1, because the sudden appearance of the "Previous Chapter" button means that that's what I'm clicking.

I guess we can wait and see what the users think....

DeployedToBeta

Assignee

DreamSea

Reporter

Sarken

Roadmap

Works

Priority

Medium

Affects versions

Fix versions

Components

FrontEnd

Difficulty

Easy

Milestone

Internal 0.9