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

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

On Wed, Jan 22, 2020 at 5:46 PM Aditya Toshniwal <aditya.toshniwal@enterprisedb.com> wrote:
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"


--
Thanks & Regards
Akshay Joshi
Sr. Software Architect
EnterpriseDB Software India Private Limited
Mobile: +91 976-788-8246

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

Предыдущее
От: Akshay Joshi
Дата:
Сообщение: Re: [pgAdmin4][RM#5107] Add tab navigation for tabs under explainpanel in query tool
Следующее
От: Akshay Joshi
Дата:
Сообщение: Re: [pgAdmin][RM4993] [Accessibility] Read-only controls and disabledcontrols needs to be separately identified