Who had the funny idea to turn tags to lowerCase on auto-completion in the Mastodon Web UI? That's kinda nasty. Especially if I select a tag like "AndroidAppRain" (spelled exactly like that in the suggestion) by typing "AndroidA" and let it auto-complete: "androidappRain" is *NOT* what I'd expect.
I've checked the preferences, but found nothing. Any hints on how to set this to sane defaults? Screenreaders have it easier with CamelCase…
This entry was edited (2 days ago)
Michael Downey 🧢
in reply to IzzyOnDroid ✅ • • •Cat 🐈🥗 (D.Burch)
in reply to IzzyOnDroid ✅ • • •FLOSS.social
in reply to IzzyOnDroid ✅ • • •Sounds like (perhaps) this "known" issue:
github.com/mastodon/mastodon/i…
Autocompletion of hashtags in the compose form flattens to lowercase
johnhorner (GitHub)IzzyOnDroid ✅
in reply to FLOSS.social • • •IzzyOnDroid ✅
in reply to IzzyOnDroid ✅ • • •jonw
in reply to IzzyOnDroid ✅ • • •IzzyOnDroid ✅
in reply to jonw • • •@jonw that worked before, didn't it? They are matched case-insensitive.
Don't get me wrong: normalisation is good. But not at the cost of those depending on screenreaders. @downey @admin
jonw
in reply to IzzyOnDroid ✅ • • •I think you're saying the storage and display elements would be different? Like AwesomeTag and Awesometag and awesomeTag would all be stored as awesometag?
If so, that makes sense.
IzzyOnDroid ✅
in reply to jonw • • •Autocompletion of hashtags in the compose form flattens to lowercase
johnhorner (GitHub)jonw
in reply to IzzyOnDroid ✅ • • •IzzyOnDroid ✅
in reply to jonw • • •Leeloo
in reply to IzzyOnDroid ✅ • • •As far as I know, the autocomplete suggests it as it was first typed, so if the first person who typed that tag was lazy, it will be lowercase.
Most people are lazy.
(At least that's how I recall the tutorial explained it when I signed up).
IzzyOnDroid ✅
in reply to Leeloo • • •Leeloo
in reply to IzzyOnDroid ✅ • • •I don't think hashtags are something you create. It's just a cache of whatever hashtags the server has seen.
Lile any other cache, I would expect them to time out at some point, so first seen may not even really be the first.
The Unusual Suspect
in reply to Leeloo • • •@leeloo
@IzzyOnDroid @downey This was my understanding too. I haven't tested it though, so...
#LetsTestItWithAUniqueHashTag
IzzyOnDroid ✅
in reply to The Unusual Suspect • • •DamonHD
in reply to IzzyOnDroid ✅ • • •@renchap
Indeed, this annoys me regularly also and it is very anti-#accessibility #a11y
Negative12DollarBill
in reply to IzzyOnDroid ✅ • • •IzzyOnDroid ✅
in reply to Negative12DollarBill • • •@negative12dollarbill One? At least 4 of them (2 from 2021, 2 from 2023, check here: github.com/mastodon/mastodon/i…) And if you check the linked issue: it started in 2023, had a few comments in 2024, and suddenly picked up 2025-10-02, where it takes off.
OK, towards the end, it seems like av4.6.0-alpha.1+glitch _might_ have fixed it: "it keeps what I have typed so far, and appends [the rest from the suggestion]". 🤞
Autocompletion of hashtags in the compose form flattens to lowercase
johnhorner (GitHub)The Turtle
in reply to IzzyOnDroid ✅ • • •🌸 lily 🏳️⚧️ θΔ ⋐ & ∞
in reply to IzzyOnDroid ✅ • • •IzzyOnDroid ✅
in reply to 🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ • • •🌸 lily 🏳️⚧️ θΔ ⋐ & ∞
in reply to IzzyOnDroid ✅ • • •IzzyOnDroid ✅
in reply to 🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ • • •🌸 lily 🏳️⚧️ θΔ ⋐ & ∞
in reply to IzzyOnDroid ✅ • • •IzzyOnDroid ✅
in reply to 🌸 lily 🏳️⚧️ θΔ ⋐ & ∞ • • •@tauon Nice idea. I happen to know, as I created BOTH tags, and BOTH of them CamelCase. And I have a filtered tab in the (advanced) UI of the web interface, where it's also spelled CamelCase.
But, if I follow the tag as you suggested, it's spelled ENTIRELY lowercase. Again nonsense then that the completion part would be camelCase then.
(1/2)
IzzyOnDroid ✅
in reply to IzzyOnDroid ✅ • • •(2/2) @tauon now let's go to my featured tags page, and it gets even weirder: the two mentioned tags are, as expected, spelled CamelCase. But at the end of the screenshot, you'll see "reproduciblebuilds", which I did not create, all lower case (while I use it "reproducibleBuilds", so folks using screenreaders have it easier).
I'd say someone messed this up majestically…
TheCoolest
in reply to IzzyOnDroid ✅ • • •Instance admins and moderators can change the capitalization of hashtags on their instance on a per-hashtag basis. I've been doing this on my instance, manually CamelCasing every hashtag that makes it to trending.
Instances default to using the hashtag capitalization which matches the first use of the hashtag the instance came across.
IzzyOnDroid ✅
in reply to TheCoolest • • •@TheCoolest Thanks! But why then does the instance I'm on, where I created the hashtag (at lease as far as I remember), not stick to the CamelCase I've used for it? 🤔
But let's see: @downey @admin could you try that for one (or both) of "IzzyOnDroid" and/or "AndroidAppRain", so we can verify? I'm 100% sure I created both hashtags, but I'm not 100% sure whether I did so before or after I migrated here from MastodonTechnology.
Nazo
in reply to IzzyOnDroid ✅ • • •Everything has it easier with camel case. Even without a screen reader it's orders of magnitude easier to mentally process tags that use camel case.
All I can come up with so far is you must do them manually first. Type the whole thing in manually, then it won't modify them to lowercase even if you click (though at that point clicking does nothing but add a space.)