Refined-github: `Scroll to bottom` button for Issue comments page

[vjpr]

Often I receive a notification in Gitify or an email that a new comment has been made. I click on the link and I then have to scroll to the bottom of the issue to see the update.

A button at the top to jump to the bottom would be great.

[hkdobrev]

BTW just noticed today, GitHub provides a jump to bottom link on mobile now.

[ghost]

My 2 cents: I personally would not really need this, as I just press the End button on my keyboard to jump to the bottom of the page in those scenarios. I forgot how to do the same thing on Mac, but I am sure it's possible. What do the others think?

[hkdobrev]

I constantly do this with ⌘+↓ on macOS. I don't really use jump to top/bottom buttons on websites. On mobile it's sometimes useful and I appreciate GitHub adding it, but I won't be using it on Desktop.

[hkdobrev]

Also, since the OP issue is about email notifications, GitHub notifications in both emails and website include links to a direct timestamp so this is mostly taken care of. If 3rd party tools are not doing that, this is mostly a problem with them.

[jgierer12]

I think this is useful sometimes, for example if you want to add a comment without reading the whole discussion or quickly check on the current status of an issue. @hkdobrev maybe take a look at how I implemented it in #904 and see if that would be acceptable for you. It doesn't really add too much clutter to the UI, so if you don't need it you can just ignore it.

[fregante]

I don't think I ever used this button. Can we drop it? Like @hkdobrev said:

I constantly do this with ⌘+↓ on macOS. I don't really use jump to top/bottom buttons on websites. On mobile it's sometimes useful and I appreciate GitHub adding it, but I won't be using it on Desktop.

RGH removes buttons that have shortcuts (e.g. in the editor toolbar) and here we're doing the opposite 😅

[Stanzilla]

@bfred-it that's not a good enough reason to drop it, I'd prefer clicking a ui element over using a key combination sometimes.

[dwijnand]

Me too. One specific difference to the example given (removing buttons that have shortcuts) is that is done with a Refined GitHub feature, which can be disabled.

Given this button is present on mobile, could this remain as a feature in RGH, perhaps disable by default so users may opt-in to using it?

[fregante]

Given this button is present on mobile

Mobile doesn't have keyboard shortcuts

[dwijnand]

You're right. Nonetheless, the user experience I'm presenting is that I was used to having a UI button available in both views.

Perhaps @Stanzilla and I represent only a small minority, compared to @hkdobrev and @bfred-it, and we should just retrain our muscle memory.

[yakov116]

I happen to use this all the time. Even though I am a keyboard fanatic _sometimes_ my mouse is in my hand

[equinox]

Would it really hurt that much adding this as an optional setting? Through this issue and the one referenced right above this, you can see at least a good handful of users want this (myself included) ...

[grahamperrin]

Switching from Waterfox Classic (with an old version of Refined GitHub) to Firefox.

I miss this feature.

IIRC the keyboard-only approach sometimes goes too far, causing the final (bottom) comment to not appear as it should.