Closed Bug 480960 Opened 15 years ago Closed 15 years ago

while trying to use litmus, I noticed the radio buttons on the forms do not get marked

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Maemo
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jmaher, Unassigned)

References

Details

I found that when we click on a radio button (maemo only) it doesn't fill in the bubble and confuses the end user.  It appears that we do submit the value when the form is submitted.

The was found while trying to view litmus on the device.
After clicking on a radio button, if you pan or scroll did it appear checked?
(In reply to comment #1)
> After clicking on a radio button, if you pan or scroll did it appear checked?

Not for me
Update: I applied the patch in bug 487693 and now I see a different behavior:
* If I click directly on the radio button, it is updated correctly.
* If I click on the label associated with the radio button, the radio is not updated.
Depends on: 487693
(In reply to comment #2)
> (In reply to comment #1)
> > After clicking on a radio button, if you pan or scroll did it appear checked?
> 
> Not for me

Actually, in a build without the patch in bug 487693, the radio is updated after a pan. Clicking on the radio or clicking on the label both update after a pan.
Mark, when you say updated after a pan, do you mean checked or focused? 

On my build it's just focused (I have include a workaround in bug 492831) due of the inner way of the label element to handle the 'for' atttribute. I suppose we can do a patch directly in ContentClickingModule but that seems to be an exception only for the label element.
I was able to see this work with a build from 6/24
Joel, this was fixed by the endPanning change for bug 504673 which prevented some screen updates after a click event.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Thanks for cleaning this up bcombee.  Planning on doing another test pass over the next two weeks and will verify all is good.
You need to log in before you can comment on or make changes to this bug.