- Affected App
- WoltLab Suite Forum
Good example of this is Black Rider does not get tagged.
Good example of this is Black Rider does not get tagged.
Select the name from the dropdown that appears while typing or put the name between ' e.g.
@'Adam Howard'
Select the name from the dropdown that appears while typing or put the name between ' e.g.
@'Adam Howard'
Yes it works if you select it or if you add single quotes, but ideally it should work if I type it out manually.
On a mobile, selecting from a long list on a busy community will not be possible, plus the moment you add the SPACE for the name, the list vanishes so you can't even narrow it down. And finally, most people will not think to us ' ' around a name after already typing @ assuming that is all that is needed (as it should be).
So I'm not saying your method doesn't work (it does), but it should be improved upon
So... How would you improve it?
So... How would you improve it?
Really simple really, names with spaces would tag just as easily with names without spaces.
@SoftCreatR works just fine typing it out
Black Rider however seems to not function when typed out
You want the user's experience to be free flowing.
Really simple really, names with spaces would tag just as easily with names without spaces.
And how yould you determine wether the second word after the @-Sign is not a word, but the second part of the user name? How would you do that when the user has a three part name, or even more (4, 5, n)?
This sounds like a job for witchcraft.
EDIT: Looks like IPS has not yet discovered witchcraft, but XF does seem to have figured something out. I'm a bit curious as to how XF determines who is being tagged.
And how yould you determine wether the second word after the @-Sign is not a word, but the second part of the user name? How would you do that when the user has a three part name, or even more (4, 5, n)?
Unknown, but it works in another development (would rather not name that development)
(would rather not name that development)
XenForo?
In general we're a bit sensitive when it comes to new features, we usually pick the safer route. The current approach prevents a lot of possible false matches, but on the other hand it's not always working when it is intended to be.
Using the dropdown (which implicitly sets the delimiters) prevents such false positives, just like @MysteryCode mentioned, consider this:
Let's assume you want to mention user A and write something after it:
Without any form of delimiters, the system will either match on @Mystery Code even though the user most likely wanted to mention @Mystery. Delimiters solve this by precisely providing a string, preventing any guesses. The example above might look a bit constructed, but during the internal development phase we came across many different cases where an automatic guess would fail. That said, unless there are delimiters, spaces and equal symbols mark the end of the string.
Especially the dropdown disappearing once you type in a space is bad and we want to improve that with Burning Board 4.1.
If you know how the name will go on you can simply use underscore:
just type @Black Rider (as seen in screenshot and it works perfectly.
Will this help solving your problem?
You don't get the drop down box on mobile site
@Black Rider sent with mobile
On android, it won't work without using the "Desktop Mode", because of the editor which isnt available for android devices by default.
On android, it won't work without using the "Desktop Mode", because of the editor which isnt available for android devices by default.
You don't get the drop down box on mobile site
This shouldn't be a problem in WBB 4.1
Redactor (4.1's new editor) is A LOT more mobile friendly than the current CKeditor (small and lightweight too, so faster loading).
Don’t have an account yet? Register yourself now and be a part of our community!