Skip to content

Conversation

@nieblara
Copy link
Contributor

@nieblara nieblara commented Jan 30, 2026

Description

What does this PR do?

Addresses REL-11957 - Improves the "clear override" UX which was reported as challenging to use (the small cyan dot wasn't obviously clickable).

This PR implements two alternative UX options, gated behind LaunchDarkly feature flags in the developer-toolbar project:

  1. Option A - Hover Reveal (clear-override-hover-reveal): The indicator expands on hover to show "Clear" text, making the action more discoverable while preserving space when not interacting.

  2. Option C - Icon Button (clear-override-icon-button): Replaces the small dot with a recognizable clear/X icon button that is universally understood as a remove action.

Both flags default to false, keeping the original dot indicator as the fallback behavior.

Type of Change

  • 🐛 Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 📚 Documentation (changes to documentation only)
  • 🔧 Refactor (code change that neither fixes a bug nor adds a feature)
  • 🎨 Style (formatting, missing semicolons, etc; no production code change)
  • Performance (code change that improves performance)
  • Test (adding missing tests, refactoring tests; no production code change)
  • 🔨 Chore (updating grunt tasks, build process, etc; no production code change)

Human Review Checklist

  • Verify feature flag keys match LaunchDarkly configuration (clear-override-hover-reveal, clear-override-icon-button)
  • Review flag priority logic: icon button takes precedence if both flags are enabled
  • Check CSS hover states and animations work as expected
  • Consider if unit tests should be added for the new component variants

Screenshots/Videos

Screenshots not available - enable the feature flags in the developer-toolbar project to test the new UX options.


Link to Devin run: https://app.devin.ai/sessions/ba2f0534579942989f3a85721e0ca681
Requested by: Ramon Niebla (@nieblara)

Implements two new UX options for the clear override action, gated behind
LaunchDarkly feature flags:

Option A (clear-override-hover-reveal): Compact badge that expands on hover
to show 'Clear' text, making the action more discoverable while preserving
space when not interacting.

Option C (clear-override-icon-button): Replaces the small dot with a
recognizable clear/X icon button that is universally understood as a
remove action.

Both options are disabled by default, with the original dot indicator
remaining as the fallback.

Addresses REL-11957

Co-Authored-By: Ramon Niebla <rniebla@launchdarkly.com>
@nieblara nieblara requested review from a team and pranjal-jately-ld as code owners January 30, 2026 02:18
@devin-ai-integration
Copy link
Contributor

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

Replaces two boolean flags with a single multivariate flag
'clear-override-ux-variant' that supports traffic splitting between:
- 'default': Original dot indicator
- 'hover-reveal': Expands on hover to show 'Clear' text
- 'icon-button': Recognizable X icon button

This makes it easier to run experiments and split traffic between variants.

Co-Authored-By: Ramon Niebla <rniebla@launchdarkly.com>
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 this pull request may close these issues.

2 participants