Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bad autocomplete for !community@instance #2803

Open
4 tasks done
Die4Ever opened this issue Nov 9, 2024 · 1 comment
Open
4 tasks done

Bad autocomplete for !community@instance #2803

Die4Ever opened this issue Nov 9, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@Die4Ever
Copy link
Contributor

Die4Ever commented Nov 9, 2024

Requirements

  • This is a bug report, and if not, please post to https://lemmy.ml/c/lemmy_support instead.
  • Please check to see if this issue already exists.
  • It's a single bug. Do not report multiple bugs in one issue.
  • It's a frontend issue, not a backend issue; Otherwise please create an issue on the backend repo instead.

Summary

Typing [email protected] gives the autocomplete for !fedigrow[[email protected]](https://lemm.ee/c/fedigrow), which is unnecessary since all frontends correctly handle the plain [email protected] (I think even Mbin handles this correctly)

And the autocomplete incorrectly takes you to a remote instance. Also the autocomplete incorrectly shows the community name twice

Screenshot_20241109-160005
shows the community name twice.

Steps to Reproduce

  1. Type ![email protected]
  2. Click autocomplete
  3. See incorrect markdown
  4. Click Preview and see incorrect result

Technical Details

Tested in Chrome and Firefox

Discussion here: https://lemmy.world/post/21832647

Lemmy Instance Version

0.19.5

Lemmy Instance URL

programming.dev

@Die4Ever Die4Ever added the bug Something isn't working label Nov 9, 2024
@DraconicNEO
Copy link

We really just need to stop having it autocorrect to a URL embed via []() and allow people to just type ![email protected] and autocorrect to the community without embedding the link as a link format. Especially since the backend already handles annotating the community links already without needing to do that and makes them functional on any instance, but directly linking hardcodes them to that instance which is a poor choice for remote users who will just get redirected there instead of the community on their own instance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants