Skip to content
This repository has been archived by the owner on Jul 30, 2019. It is now read-only.

Should readonly (or something like it) work for non-text form elements? #837

Closed
chaals opened this issue Mar 29, 2017 · 1 comment
Closed

Comments

@chaals
Copy link
Collaborator

chaals commented Mar 29, 2017

Input types that are not supported, such as datetime currently, are presented as text inputs, and therefore readonly applies.

It is also, apparently repeatedly (citation needed), allowed to apply in initial implementations of new widgets.

The use case is allowing preview of a control which will be submitted - disabled means the control won't be submitted, requiring the developer to add e.g. a hidden mirror of the content if they present a disabled control.

There are several issues that have looked at this before: #89, #91, #92, and http://github.com/whatwg/html/issues/2311

@siusin
Copy link
Contributor

siusin commented Jul 29, 2019

Thanks.

We're closing this issue on the W3C HTML specification because the W3C and WHATWG are now working together on HTML, and all issues are being discussed on the WHATWG repository.

If you filed this issue and you still think it is relevant, please open a new issue on the WHATWG repository and reference this issue (if there is useful information here). Before you open a new issue, please check for existing issues on the WHATWG repository to avoid duplication.

If you have questions about this, please open an issue on the W3C HTML WG repository or send an email to public-html@w3.org.

@siusin siusin closed this as completed Jul 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants