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

[feature] updated content binding value is ignored #23

Closed
alex3683 opened this issue Dec 1, 2017 · 4 comments
Closed

[feature] updated content binding value is ignored #23

alex3683 opened this issue Dec 1, 2017 · 4 comments

Comments

@alex3683
Copy link

alex3683 commented Dec 1, 2017

Feature

Actually, I don't know if this is a bug or a feature request. I must admit that I simply expected this to be working. :-) Now the actual issue:
When binding the tooltip to a value, the tooltip renders with the first value it reads from the binding. Whenever the binding's value changes henceforth, that change is not reflect. The tooltip still shows the initial value of the binding. I made an example here: https://codepen.io/anon/pen/EbGbgL
Simply edit the value in the input and you'll see, that the tooltip won't show that new text.

@hekigan
Copy link
Owner

hekigan commented Dec 1, 2017

The code to make it work from your example is the following:

<span v-tooltip="{content: tooltipText}" class="tooltip-origin">tooltip</span>

But I understand why it could be confusing that the simple way does not work the same way.
I will update that to be able to either soon.

This comment was helpful, since I did not notice that issue, thank you.

@traykovn
Copy link

traykovn commented Dec 2, 2017

I tried exactly that:

<span v-tooltip="{content: tooltipText}" class="tooltip-origin">tooltip</span>

And it didn't work. This was the first thing I thought of, since it is intuitive, but didn't manage to change the value.

@traykovn
Copy link

traykovn commented Dec 2, 2017

Actually this works:

<span v-tooltip="{content: tooltipText}" class="tooltip-origin">tooltip</span>

It wasn't working because of my mistake.

hekigan added a commit that referenced this issue Dec 5, 2017
- #25 : Problem with default placement bug
- #23 : updated content binding value is ignored enhancement
@hekigan
Copy link
Owner

hekigan commented Dec 5, 2017

Done!

@hekigan hekigan closed this as completed Dec 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants