Open
Bug 1035790
Opened 10 years ago
Updated 2 years ago
Hidden checkbox and radio values from visible labels are mouse accessible only, not keyboard
Categories
(Core :: Layout: Form Controls, defect)
Tracking
()
UNCONFIRMED
People
(Reporter: laszlo.janszky, Unassigned)
Details
(Keywords: testcase)
Attachments
(1 file)
2.13 KB,
text/html
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0 (Beta/Release)
Build ID: 20140605174243
Steps to reproduce:
I created a nested select input based on checkboxes (or radio buttons). I hid the inputs and displayed only the labels with css. I added tabindex to each label, to access them with keyboard.
note: Other browsers have the same inconsistent behavior. By chrome the tabindex does not work, and MSIE scrolls to the label by pressing space... Should I send a bug report to them as well? Is this an intentional behavior because of security reasons?
Actual results:
When I click on a label, it toggles the value of the checkbox as expected. I can focus on the labels using tabs, but they don't do anything by pressing enter or space.
Expected results:
It should toggle the value of the hidden checkbox by pressing enter or space when the label is in focus.
Comment 1•10 years ago
|
||
confirmed
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:33.0) Gecko/20100101 Firefox/33.0
Build ID: 20140713030204
[testday-20140714]
Comment 2•10 years ago
|
||
Reproduced with 2014-07-14-03-02-01-mozilla-central-firefox-33.0a1.ru.linux-x86_64.
QA Whiteboard: [bugday-20140714]
Component: Untriaged → Layout
Keywords: testcase
OS: Windows 7 → All
Product: Firefox → Core
Summary: Checkbox and radio values from labels are mouse accessible only → Hidden checkbox and radio values from visible labels are mouse accessible only, not keyboard
Updated•10 years ago
|
Component: Layout → Layout: Form Controls
Flags: needinfo?(bugs)
Comment 3•10 years ago
|
||
The spec is rather vague here
"The label element's exact default presentation and behavior, in particular what its activation behavior might be, if anything, should match the platform's label behavior."
And in an example
"For example, on platforms where clicking a checkbox label checks the checkbox, clicking the label in the following snippet could trigger the user agent to run synthetic click activation steps on the input element, as if the element itself had been triggered by the user"
It is not clear to me what the behavior should be. OSX has odd focus handling, so there
keyboard accessible probably wouldn't work anyway...
László, you may want to send email to whatwg mailing list about this.
Flags: needinfo?(bugs)
Comment 4•10 years ago
|
||
(In reply to Olli Pettay [:smaug] from comment #3)
> OSX has odd focus
> handling, so there
> keyboard accessible probably wouldn't work anyway...
Or maybe it would. Can't recall now the details of tabindex + label there.
Reporter | ||
Comment 5•10 years ago
|
||
(In reply to Olli Pettay [:smaug] from comment #3)
> The spec is rather vague here
> "The label element's exact default presentation and behavior, in particular
> what its activation behavior might be, if anything, should match the
> platform's label behavior."
>
> And in an example
> "For example, on platforms where clicking a checkbox label checks the
> checkbox, clicking the label in the following snippet could trigger the user
> agent to run synthetic click activation steps on the input element, as if
> the element itself had been triggered by the user"
>
> It is not clear to me what the behavior should be. OSX has odd focus
> handling, so there
> keyboard accessible probably wouldn't work anyway...
>
> László, you may want to send email to whatwg mailing list about this.
Sorry, I don't know that mailing list, I just sent a report, that's all. I think it would be logical, if the checkbox would be keyboard accessible using the label, since it is mouse accessible currently. But that's just an opinion, I know nothing about the specification you mentioned... I intend to report this issue by the other browsers as well, if you decide to fix it. If not, that's okay for me.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•