I'm not sure where to report suggestions or problematic behaviors to the Mastodon development team.

This one is an intentional behavior, not a bug.

To help those who use screen readers, we are suggesting to newcomers that they use on hashtags so that screen readers read the text correctly. However, Mastodon's post compose window often changes camel case hashtags to all lower case. It seems to do this if the hashtag is a popular one.

It might be good to leave hashtags alone, as written by the user, instead of overriding with what Mastodon thinks the user meant to type.

@shuttersparks you can file an issue in the official issue tracker starting here:

FWIW instance admins are able to improve this by manually re-casing the hashtags in their admin interface, but it's a long and tedious process and has to be repeated with new hashtags that pop up.

@shuttersparks On, it SUGGESTS the all small letters, but doesn't override my typing

@jrosen707 That would be okay. Sometimes I've typed in camel case and when I do a quick proof before hitting Toot I notice they've changed to lower case. Exactly how and when that happens I'm not sure.

What do now is recheck and fix the hashtags immediately before hitting Toot and they "stick".

@shuttersparks What user interface are you using? The website page or a phone app?

@EricFielding Sorry for the delay in responding. I'm using the web interface.

@shuttersparks This is a good shout and I hope an adjustment is made. Camelcase is better for sighted users as well when its the original intention.

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.