Originally reported in 2024 on Discord (link). I vaguely remember getting a dev reply saying they've made a ticket and will be working on it, but can't seem to find the reply anymore.
I'm trying to use https://x.com/search?q=(%23かんたべりーでいず)(from:guardiantalesjp) as the link to Official Raw in https://mangadex.org/title/4df219da-4b5f-48ea-9fac-23641ae8a584, since it's the official publication medium.
Since the hashtag character (
But annoyingly, the frontend always normalizes that combination into a single
Which breaks the Twitter/X hashtag search query:
Because the browser treats the unescaped
The intended behavior should be:
I'm trying to use https://x.com/search?q=(%23かんたべりーでいず)(from:guardiantalesjp) as the link to Official Raw in https://mangadex.org/title/4df219da-4b5f-48ea-9fac-23641ae8a584, since it's the official publication medium.
Since the hashtag character (
#) needs to be escaped when using inside URL queries, I've tried percent-encoding it in multiple ways:%23-> #%2523-> %23%25%32%33-> %23
But annoyingly, the frontend always normalizes that combination into a single
#:Which breaks the Twitter/X hashtag search query:
Because the browser treats the unescaped
# as the URI fragment marker, and everything after it is ignored.The intended behavior should be: