- From: James Nurthen <james.nurthen@oracle.com>
- Date: Wed, 8 Jun 2016 14:06:26 -0700
- To: public-aria@w3.org
- Message-ID: <c0071f9c-ce5a-31ce-c7da-d675443cbf4e@oracle.com>
I also have to ask why the multi-line restriction. If I choose to wrap a field which may contain a passphrase why would this be an issue? On 6/8/2016 1:57 PM, Rich Schwerdtfeger wrote: > What is the use case for having a read only password? > > Rich > > Sent from my iPhone > >> On Jun 7, 2016, at 5:40 PM, Joanmarie Diggs <jdiggs@igalia.com> wrote: >> >> Proposed text: >> >> Authors SHOULD limit the use of the password role to single-line >> elements which are editable. Authors MAY use the password role on >> elements which are not currently editable due to application-specific >> conditions. However, in that instance, authors MUST indicate that the >> element is read only by setting aria-readonly to true or using the >> appropriate native host language attribute. User agents MUST ignore the >> password role when it is applied to elements which are neither editable >> nor explicitly marked as read only. >> >> * https://github.com/w3c/aria/commit/fe849c8c >> * https://rawgit.com/w3c/aria/action-2080/aria/aria.html#password >> >> --joanie >> >> -- Regards, James Oracle <http://www.oracle.com> James Nurthen | Principal Engineer, Accessibility Phone: +1 650 506 6781 <tel:+1%20650%20506%206781> | Mobile: +1 415 987 1918 <tel:+1%20415%20987%201918> | Video: james.nurthen@oracle.com <sip:james.nurthen@oracle.com> Oracle Corporate Architecture 500 Oracle Parkway | Redwood Cty, CA 94065 Green Oracle <http://www.oracle.com/commitment> Oracle is committed to developing practices and products that help protect the environment
Received on Wednesday, 8 June 2016 21:07:00 UTC