Update tooltip to run setup on connectedCallback instead of relying on attributeChangedCallback #1688
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
It looks like when we navigate using a Turbo Frame in dotcom, due to some Turbo internals,
attributeChangedCallback
runs before the element is added to the DOM tree. This causescontrol
to not be found (since it's also not in the tree) and the setup is skipped. In this case,control
will not have the correctaria-
attributes.With this change, I'm guaranteeing that the setup always runs when the
tool-tip
connects to the page.Integration
Nope, this should be a no-op in terms of functionality
Merge checklist