-
Notifications
You must be signed in to change notification settings - Fork 11
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
Unique tags are only displayed once per Map Show view #81
Comments
Seems we need to call
… once the modal is closed. Like this:
|
I was wondering what that method was for. Where do you think is best to catch the modal closing event? |
Probably attach handler for the close button when the tagging view is initialized.
Or similar. |
It doesn't appear that you can add a click() handler to a link, because they're they're already tied to their own click() event. I'll look for a workaround. |
Ah, you know what? You could also bind the reset to when the modal is opened, because that happens in the annotation view, i.e. in the |
It seems that if you add an inline event click handler for the link, it works fine, so that's what I did. So now it reads: <a class="close" data-dismiss="modal" onclick="window.tagging_view.reset();">×</a> |
It's not pretty, but it works ;) I mean, we don't have these kinds of inline handlers anywhere else, and it's a little old-fashioned to use them at all, but that is something for "code quality", not a bug. |
Yeah, I realize that it's not as elegant a solution as it could be, but there are bigger fish to fry for getting the experiment environment ready to run tests. I'll reopen this as a code quality issue. |
This is kind of a strange bug to describe, but basically, if you do the following:
Then no tags are displayed (though the Annotation Controller still seems to be generating them). This is particularly an issue with the user-suggest condition, where all tags are drawn from the same tag pool, so if a user changes their mind after creating an initial annotation and wants to do another one on the same map, they will receive limited to no tag suggestions.
I believe the root of the problem is that in the javascript TaggingView file, only unique tags are displayed, but the TaggingView is loaded only once per show view. It would seem that the list of tags in the TaggingView perpetuates until the map is rendered again.
The text was updated successfully, but these errors were encountered: