fix: address ArticleTeaser hover bug#886
Merged
Merged
Conversation
Contributor
Author
|
Before and after: before-and-after.mov |
Contributor
Author
|
Whoops, forgot to push |
curlyfriesplease
approved these changes
May 18, 2026
|
🎉 This PR is included in version 8.73.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR description
What is it doing?
Tweaks markup and styles to ensure hover states are being applied where they should've been from the start (i.e. the anchor), and solves the "infinite bounce" bug brought about by apply positional transforms to a moving target; requiring an additional wrapper to encapsulate all of the content inside the anchor.
Why is this required?
Better UX
link to Jira ticket:
No new ticket
Quick Checklist:
My PR title follows the Conventional Commit spec.
I have filled out the PR description as per the template above.
I have added tests to cover new or changed behaviour.
I have updated any relevant documentation.
Important! - lastly, make sure to squash merge...