[pgAdmin][RM4993] [Accessibility] Read-only controls and disabledcontrols needs to be separately identified

Поиск
Список
Период
Сортировка
От Aditya Toshniwal
Тема [pgAdmin][RM4993] [Accessibility] Read-only controls and disabledcontrols needs to be separately identified
Дата
Msg-id CAM9w-_n8hzWzjP33g-KFy-BpBk-t6_u26U7M8atkHD8z4+3nyw@mail.gmail.com
обсуждение исходный текст
Ответы Re: [pgAdmin][RM4993] [Accessibility] Read-only controls and disabledcontrols needs to be separately identified  (Akshay Joshi <akshay.joshi@enterprisedb.com>)
Re: [pgAdmin][RM4993] [Accessibility] Read-only controls and disabledcontrols needs to be separately identified  (Akshay Joshi <akshay.joshi@enterprisedb.com>)
Список pgadmin-hackers
Hi Hackers,

Attached is the patch to allow input controls to be set as readonly instead of disabled.
I've also changed the code for the nodes to make sure properties tab have readonly fields wherever applicable. This will allow tab navigation in properties tab and also allow screen readers to read it.
Please note that, I've not visited each and every node create/edit dialog to identify what should be readonly or what should be disabled as it depends on business logic. The patch is mainly for the properties tab.

Kindly review.

--
Thanks and Regards,
Aditya Toshniwal
pgAdmin Hacker | Sr. Software Engineer | EnterpriseDB India | Pune
"Don't Complain about Heat, Plant a TREE"
Вложения

В списке pgadmin-hackers по дате отправления:

Предыдущее
От: Nick Barnes
Дата:
Сообщение: Error when editing char(n)[] cells
Следующее
От: Akshay Joshi
Дата:
Сообщение: [pgAdmin][RM2554] declarative partitioning - support for multi-level partition