Back to bug 8062

Who When What Removed Added
ossman 2022-12-29 11:17:03 CET Blocks 3854
ossman 2023-01-03 13:14:40 CET Target Milestone --- MediumPrio
samuel 2023-01-23 15:46:13 CET CC samuel
samuel 2023-02-28 11:05:29 CET Acceptance Criteria * Controls should have labels when the purpose of the control by itself isn't clear.

* Clicking a label next to a control should activate the control (check the checkbox, focus the text-input etc.)

* Labels should not be focusable using the keyboard. They should not receive a focus-outline and should be skipped in the tab-cycle order.

* Where we have disabled controls, the connected label should also appear disabled.
Target Milestone MediumPrio 4.15.0
Assignee bugzilla-qa samuel
Summary Checkbox labels aren't clickable Web Admin input labels aren't clickable
Keywords prosaic
alexander.zeijlon 2023-03-13 14:02:49 CET CC alexander.zeijlon
Assignee samuel alexander.zeijlon
alexander.zeijlon 2023-03-16 12:44:16 CET Acceptance Criteria * Controls should have labels when the purpose of the control by itself isn't clear.

* Clicking a label next to a control should activate the control (check the checkbox, focus the text-input etc.)

* Labels should not be focusable using the keyboard. They should not receive a focus-outline and should be skipped in the tab-cycle order.

* Where we have disabled controls, the connected label should also appear disabled. 		* Controls should have labels when the purpose of the control by itself isn't clear.

* Clicking a label next to a control should activate the control (check the checkbox, focus the text-input etc.)

* Labels should not be focusable using the keyboard. They should not receive a focus-outline and should be skipped in the tab-cycle order.

* Where we have disabled controls, the connected label should also appear disabled.

* Labels that relate to a set of control/input elements should map to the container that holds them.

* IDs added to elements that labels map to must be unique.
alexander.zeijlon 2023-03-16 12:58:05 CET Status NEW RESOLVED
Resolution --- FIXED
alexander.zeijlon 2023-03-16 13:00:21 CET See Also https://bugzilla.cendio.com/show_bug.cgi?id=8056
alexander.zeijlon 2023-03-22 13:43:02 CET Acceptance Criteria , the connected label should also appear disabled.

* Labels that relate to a set of control/input elements should map to the container that holds them.

* IDs added to elements that labels map to must be unique. 		, the connected label should also appear disabled.

* Labels that relate to a set of control/input elements should map to the container that holds them.

* IDs added to elements that labels map to must be unique.

* Table cells that are visual labels for input elements should be <th> instead of <td> since we have special styling for these.

* HTML labels should map to labelable control elements.

* HTML labels should not map to containers that hold multiple control elements.
Resolution FIXED ---
Status RESOLVED REOPENED
Acceptance Criteria * Controls should have labels when the purpose of the control by itself isn't clear.

* Clicking a label next to a control should activate the control (check the checkbox, focus the text-input etc.)

* Labels should not be focusable using the keyboard. They should not receive a focus-outline and should be skipped in the tab-cycle order.

* Where we have disabled controls 		* Controls should have labels when the purpose of the control by itself isn't clear.

* Clicking a label next to a control should activate the control (check the checkbox, focus the text-input etc.)

* Labels should not be focusable using the keyboard. They should not receive a focus-outline and should be skipped in the tab-cycle order.

* Where we have disabled controls
alexander.zeijlon 2023-03-22 15:47:06 CET Resolution --- FIXED
Status REOPENED RESOLVED
alexander.zeijlon 2023-03-23 12:30:21 CET Resolution FIXED ---
Status RESOLVED REOPENED
alexander.zeijlon 2023-03-23 12:31:04 CET Status REOPENED RESOLVED
Resolution --- FIXED
linma 2023-03-28 09:18:41 CEST CC linma
Keywords linma_tester
linma 2023-03-29 16:25:04 CEST Acceptance Criteria * Controls should have labels when the purpose of the control by itself isn't clear.

* Clicking a label next to a control should activate the control (check the checkbox, focus the text-input etc.)

* Labels should not be focusable using the keyboard. They should not receive a focus-outline and should be skipped in the tab-cycle order.

* Where we have disabled controls, the connected label should also appear disabled.

* Labels that relate to a set of control/input elements should map to the container that holds them.

* IDs added to elements that labels map to must be unique.

* Table cells that are visual labels for input elements should be <th> instead of <td> since we have special styling for these.

* HTML labels should map to labelable control elements.

* HTML labels should not map to containers that hold multiple control elements. 		* Controls should have labels when the purpose of the control by itself isn't clear.

* Clicking a label next to a control should activate the control (check the checkbox, focus the text-input etc.)

* Labels should not be focusable using the keyboard. They should not receive a focus-outline and should be skipped in the tab-cycle order.

* Where we have disabled controls, the connected label should also appear disabled.

* IDs added to elements that labels map to must be unique.

* Table cells that are visual labels for input elements should be <th> instead of <td> since we have special styling for these.

* HTML labels should map to labelable control elements.

* HTML labels should not map to containers that hold multiple control elements.
linma 2023-03-29 16:30:45 CEST Status RESOLVED CLOSED
alexander.zeijlon 2023-04-21 13:40:06 CEST Status CLOSED REOPENED
Resolution FIXED ---
alexander.zeijlon 2023-04-21 14:38:33 CEST Resolution --- FIXED
Status REOPENED RESOLVED
frifl 2023-04-26 12:25:42 CEST CC frifl
Keywords frifl_tester
frifl 2023-04-26 13:47:02 CEST Status RESOLVED CLOSED

Back to bug 8062