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

Allow target to be manually set #144

Open
odejesush opened this issue Jan 4, 2019 · 0 comments · May be fixed by #145
Open

Allow target to be manually set #144

odejesush opened this issue Jan 4, 2019 · 0 comments · May be fixed by #145

Comments

@odejesush
Copy link

Allow the target of the tooltip to be manually set through the target attribute to allow the tooltip to be anchored to the given element.

I have a somewhat specific problem in which I need to use a common paper-tooltip for multiple targets that are not siblings of the common paper-tooltip element. The reason for this design choice was to fix a bug where the tooltip was cut off when rendering inside of an iron-list element. The problem is best described by this Chromium bug: 870202, and the fix for this bug was implemented by the change 1176586. However, in the fix, the private _target property of the tooltip is directly accessed and assigned the target that is passed up to the parent of the common tooltip from the children.

Because of this bug, in my own implementation of a new element with similar structure, I have to do the same thing to prevent the tooltip from being cut off.

Who will use the feature?

Any developer that has a similar problem with the tooltip being cut off by other elements, or any developer who would like to use a common tooltip for targets that are children of siblings.

When will they use the feature?

This feature can be used when the target element is known, and it is not a sibling of the paper-tooltip element.

What is the user's goal?

To prevent the fix for the specific bug where the tooltip is being cut off from directly accessing a private property of paper-tooltip.

@odejesush odejesush linked a pull request Jan 4, 2019 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant