Mastodon: There is no hotkey for expanding a toot with a CW

[iliana]

Fully using Mastodon with a keyboard isn't quite usable without being able to expand a toot with a CW.

May I suggest shift+enter?

(I can hit Tab four times to focus the Show More button and hit space as a work around. That's certainly not ideal.)

---

• [x] I searched or browsed the repo’s other issues to ensure this is not a duplicate.
• [ ] This bug happens on a tagged release and not on master (If you're a user, don't worry about this).

[claiire]

Tbh I really think this should be a higher priority thing.

Ensuring that a website is usable with the keyboard only is an important accessibility feature, and shortcuts aren't quite complete without an expand cw shortcut.

[beatrix-bitrot]

how do you feel about space for this?

[sorin-davidoi]

It works with Enter when you focus the toggle button.

[nightpool]

I was thinking 'x'. This is really confusing for me on a daily basis
On Fri, Nov 17, 2017 at 6:26 PM Sorin Davidoi [e-mail]
wrote:

It works with Enter when you focus the toggle button.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tootsuite/mastodon/issues/5550#issuecomment-345393005,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAORV5KhlHqbDnSJg1-_zp6NFXruxm1uks5s3hY7gaJpZM4QJwIO
.

[iliana]

Hitting tab four times to focus toggle isn't good enough, frankly.

x would be reasonable to me.

I'd be happy with space but you can currently use that to scroll down a page, I think getting in the way of keys that currently do things is not a good idea.

[beatrix-bitrot]

x then, very well

[deutrino]

Is there anything standing in the way of merging this?

[sorin-davidoi]

There is nothing to merge yet, as no one opened a pull request fixing this.

[deutrino]

I meant from changes in glitch-soc/mastodon#232.

I can never get an answer from any of them about how changes might flow back upstream - I've asked regarding media previews, for example, and never gotten an answer.

[beatrix-bitrot]

@deutrino sorry about not getting back to you. there's a lot of reasons things don't make it back upstream. some have, most don't. here i think the change in functionality depended on refactoring some stuff, and was also done on a set of files that don't actually exist upstream, so it can't be merged into upstream and it's also not trivial to backport it. everyone has things they'd rather be doing.