[Feature Request] Make chapters plugin buttons available in sidebar / for shortcuts.

[adjmunro]

Hi! I really like what you did with your chapters plugin.

I currently have this in user actions: (which I wrote before the chapters plugin to get similar functionilty)

[
  {
    "code": "var url = 'https://' + document.getElementById('reader-domain').textContent.replace(/\\s+/g, ''); var parts = url.split('/'); var i = parts.length - 2; var index = parts[i].match(/\\d+/g); if (index != null) { index = index.map(Number)[0]; parts[i] = parts[i].replace(index, index + 1); var next = parts.join('/'); window.open(next, '_self').focus(); }",
    "shortcut": "Shift + ArrowRight",
    "title": "Next"
  },
  {
    "code": "var url = 'https://' + document.getElementById('reader-domain').textContent.replace(/\\s+/g, ''); var parts = url.split('/'); var i = parts.length - 2; var index = parts[i].match(/\\d+/g); if (index != null) { index = index.map(Number)[0]; parts[i] = parts[i].replace(index, index - 1); var next = parts.join('/'); window.open(next, '_self').focus(); }",
    "shortcut": "Shift + ArrowLeft",
    "title": "Previous"
  }
]

but to be quite frank, your chapters plugin/regex works much better than my hack. Javascript just isn't my forte.

But my only complaint is that the next/previous chapter links always show at the bottom of the page! This is bad when:

• Simply navigating multiple chapters at once
• Navigating mid-chapter (which sometimes happens - maybe you forgot what happened last chapter)
• The chapter has a whole load of bloat at the bottom, such as recommendations that weren't filtered out or sometimes a really long block of text by the author or a translator.
• Must navigate with a mouse click
• Have to wait for the links to become visible before you can click them - or deactivate TTS (since it prevents you from scrolling by jumping you back to the new paragraph as you try to scroll down.

Personally, I use my custom shift + right shortcut to go to the next chapter while the TTS is still running, rather than waiting for the TTS to finish reading prev/next and also slowly moving my mouse over; and then immediate use a shift + '/' shortcut to start TTS on the next chapter.

So, please make article.next / article.previous public so that I can trigger them from one of those custom user actions (or add them to the sidebar yourself as possible buttons to display and/or add shortcuts?) 🥺

Sorry, I'd submit a PR myself, but I'm from Java/Kotlin land and can barely make heads or tails of what's going on 🙃

[rNeomy]

You can already trigger the native ones from the custom action:

[
  {
    "code": "document.querySelector('#chapters a:first-of-type').click()",
    "title": "Previous Chapter"
  },
  {
    "code": "document.querySelector('#chapters a:last-of-type').click()",
    "title": "Next Chapter"
  }
]

[adjmunro]

@rNeomy Thanks for the quick response! It works really well!