A user, bts, reported an issue with hashtag autocomplete in Discourse. When typing a # symbol in a context where they don’t want to tag something, the autocomplete dialogue persists even after hitting space or return, resulting in unwanted autocompletion. bts shared a video demonstrating the issue. codinghorror suggested pressing the ESCAPE key as a workaround. bts clarified that they were simply reporting the unusual behavior to be helpful. sam confirmed that this is a bug and sam later fixed the issue with a commit to the Discourse GitHub repository.
Noticed an issue with # autocomplete when composing a reply. Basically I start typing # in a context where I don’t want to tag something (e.g. #s) but even after hitting ‘space’, or several spaces, the autocomplete dialogue still shows and if I hit ‘return’ it autocompletes when I didn’t want it to.
Note: below Dropbox video link seems to not be displaying correctly as embed. Here’s the raw URL: https://www.dropbox.com/s/dx4tlkobrx1w170/discourse-hashtag-autocomplete-bug.mov?dl=0
Use this https://www.dropbox.com/s/dx4tlkobrx1w170/discourse-hashtag-autocomplete-bug.mov?dl=1
instead of this https://www.dropbox.com/s/dx4tlkobrx1w170/discourse-hashtag-autocomplete-bug.mov?dl=0
(had already been reported by someone, now I can not find the related topic)
I mean I never said it was a major bug. Just reporting funky behavior / trying to be helpful. A space or a return should be enough to exit the autocomplete dialog. Of course do with it (or not) what you will If there’s some severity threshold for reporting stuff no worries but if so I didn’t know about it and I’m on here a lot!
If there’s some severity threshold for reporting stuff no worries but if so I didn’t know about it and I’m on here a lot!