Question:
I’ve encountered a bug with the RadioGroup component in Wix Velo that impacts the user interface’s visual feedback when interacting with a connected dataset. Despite the RadioGroup’s value being successfully updated and the corresponding radio button correctly selected, the visual indicator (selected color) for the active radio button does not appear as expected. All radio buttons remain visually unselected (white), which confuses the end-users about their current selection.
Product:
Wix Editor, VELO javascript
What are you trying to achieve:
[Explain the details of what you are trying to achieve. The more details you provide, the easier it is to understand what you need.]
What have you already tried:
everything
Additional information:
Steps to Reproduce:
- Setup: Create a RadioGroup component with 5 options, each having a label and a value.
- Dataset Connection: Connect the RadioGroup’s value to a field in a dataset, allowing it to update based on user selection.
- User Interaction: Select a radio button to update the dataset value.
- Observation: While the dataset successfully updates with the new value, and the correct radio button is programmatically selected (confirmed through debugging), the visual feedback (i.e., the selected color highlighting the active button) does not appear.
Expected Behavior:
Upon selecting a radio button, the dataset updates, and the RadioGroup visually reflects this selection by highlighting the selected radio button with a distinct color.
Actual Behavior:
The dataset updates with the new selection, but the RadioGroup does not visually highlight the selected radio button. All buttons appear unselected (white), leading to user confusion.
Impact:
This visual discrepancy undermines the UI’s intuitiveness, making it challenging for users to confirm their selections, affecting the overall user experience on the platform.
I believe this behavior might be a bug since the expected outcome of visually indicating the selected radio button is a standard behavior for such components. I’ve verified this issue across multiple browsers and devices, ruling out client-side anomalies.
Thank you for your attention to this matter.