Detect and handle spaces when tagging
Bug #324437 reported by
Paul Everitt
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| KARL3 |
Fix Released
|
Low
|
Balazs Ree | ||
Bug Description
We currently allow spaces when creating a tag. We need to make sure that isn't allowed, both server side and client side.
Next, we should decide what to do if someone does this. Do we automatically make two tags? Or do present some kind of error message?
| Changed in karl3: | |
| assignee: | nobody → ree |
| importance: | Undecided → Low |
| Changed in karl3: | |
| milestone: | none → m1 |
Revision history for this message
| Balazs Ree (ree) wrote | #1 |
| Changed in karl3: | |
| status: | New → Fix Committed |
| Changed in karl3: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Spaces are currently "invalid characters" so those tags will immediately get a yellow box.
The checking is done both on client and server.
As we discussed we don't want to allow adding space-separated tags, mainly because it complicates livesearch for the user. (Implementation wise it's implementable to search for the last word only.)