Search and Top Navigation
#10726 closed bug (fixed)
Opened December 15, 2014 01:51PM UTC
Closed October 27, 2015 01:24PM UTC
Last modified June 27, 2016 10:22PM UTC
Button: selecting text causes an inconsistent state
| Reported by: | Patrick1701 | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 1.12.0 |
| Component: | ui.button | Version: | 1.11.2 |
| Keywords: | regression | Cc: | |
| Blocked by: | Blocking: |
Description
It is possible to get a "selected" radio-choice button ui element, without really having a selected value.
See http://jsfiddle.net/gdsawfkm/4/
It seems to me, onChange events are triggered by mouse-events, not by input-element changed events, or something...
kind regards
Patrick
Attachments (0)
Change History (8)
Changed December 15, 2014 08:25PM UTC by comment:1
| keywords: | → regression |
|---|---|
| status: | new → open |
| summary: | Button RadioChoices / slipping from element or selecting text doesnt really select, but looks like → Button: selecting text causes an inconsistent state |
Changed December 16, 2014 12:05PM UTC by comment:2
... this ticket is possibly a duplicate of #9990.
Unfortunately, I'm not able to reproduce it with jsfiddle mentioned there, but it really sounds like its the same issue.
Changed December 18, 2014 08:50AM UTC by comment:3
I would appreciate to change the priority to major, and also create a fix for 1.10.5?
best regards
Patrick
Changed February 10, 2015 02:20PM UTC by comment:4
Hi all,
this issue is really a problem.
We often have users on our system reporting unexpected behaviors from the UI which shows selected radio choices, which are not submitted via form to the server, becoming persistent. Later on users find "old" data, having in mind they changed it, and submitted/saved it, but its not.
This issue is quite critical!
Please, please, provide a fix for 1.11.3!
kind regards
Patrick
Changed February 23, 2015 02:52PM UTC by comment:5
We also hit this issue, and it's pretty bed as user sees he selected something but in reality the selection hasn't made or on another one. I can reproduce on the mentioned jsbin with 10.4 and later.
A workaround we use is demonstrated in http://jsfiddle.net/kakwryLe/6/ (commented line)
Changed February 23, 2015 03:02PM UTC by comment:6
The button widget is re-written for 1.12, and the checkbox / radio functionality has been factored out into a separate widget. I just checked on the new widget and this problem does not exist there.
Changed October 27, 2015 01:24PM UTC by comment:7
| milestone: | none → 1.12.0 |
|---|---|
| resolution: | → fixed |
| status: | open → closed |
Confirmed fixed in master.
This regressed in 1.10.4 as this works fine in 1.10.3: http://jsfiddle.net/0f0ohfs1/. The fix for #7665 broke this so this ticket is possibly a duplicate of #9990.