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

fix(label): allow signposts inside labels #937

Merged
merged 5 commits into from
Jan 7, 2025
Merged

Conversation

dtsanevmw
Copy link
Contributor

PR Checklist

Please check if your PR fulfills the following requirements:

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)
  • If applicable, have a visual design approval

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

Currently if you put signposts inside labels they are not working due to that <label> be default is spreading a click event to its children and that's causing the signpost to automatically close and not appear.
Example:
If you have a label attached to an input or input inside a label and click the label - the input will get focused.

Issue Number: CDE-9 and #271

What is the new behavior?

Signposts are now working inside <label>.

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

@dtsanevmw dtsanevmw requested a review from a team September 7, 2023 03:31
@dtsanevmw dtsanevmw self-assigned this Sep 7, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Sep 7, 2023

👋 @dtsanevmw,

  • 🙏 The Clarity team thanks you for opening a pull request
  • 🎉 The build for this PR has succeeded
  • 🔍 The PR is now ready for review
  • 🍿 In the meantime, view a preview of this PR
  • 🖐 You can always follow up here. If you're a VMware employee, you can also reach us on our internal Clarity Support space

Thank you,

🤖 Clarity Release Bot

@dtsanevmw dtsanevmw force-pushed the dtsanevmw/cde-9 branch 4 times, most recently from bc86de3 to 2c719c3 Compare September 7, 2023 03:53
@dtsanevmw dtsanevmw force-pushed the dtsanevmw/cde-9 branch 2 times, most recently from 010bb33 to 4d5c056 Compare September 8, 2023 05:42
@dtsanevmw
Copy link
Contributor Author

Will wait the popover refactor #1435 to be merged

@dtsanevmw dtsanevmw force-pushed the dtsanevmw/cde-9 branch 2 times, most recently from c6928d1 to 1528a5a Compare January 7, 2025 15:34
@dtsanevmw dtsanevmw requested a review from kevinbuhmann January 7, 2025 15:36
@dtsanevmw dtsanevmw force-pushed the dtsanevmw/cde-9 branch 2 times, most recently from f755fab to 1928be8 Compare January 7, 2025 15:46
@dtsanevmw dtsanevmw merged commit 92d623e into main Jan 7, 2025
11 checks passed
@dtsanevmw dtsanevmw deleted the dtsanevmw/cde-9 branch January 7, 2025 22:23
Copy link
Contributor

github-actions bot commented Jan 7, 2025

🎉 This PR is included in version 17.5.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Copy link
Contributor

Hi there 👋, this is an automated message. To help Clarity keep track of discussions, we automatically lock closed PRs after 14 days. Please look for another open issue or open a new issue with updated details and reference this one as necessary.

@github-actions github-actions bot locked and limited conversation to collaborators Jan 22, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants