Obsolete
Status Update
Comments
al...@android.com <al...@android.com> #2
Looks like editable is used as a fallback when inputType is specified as "none", which makes it impossible to use inputType="none" by itself to make text non-editable.
de...@gmail.com <de...@gmail.com> #3
Starred.
The original issue (2854) was open in 2009, 7 years later the "editable=false" is still deprecated and there isn't any valid XML alternative to it.
As of as Android-N Dev Preview 2 the best way to achieve the expected result is to set the EditText to android:editable="false".
Is this going to have a valid alternative or should I use android:editable until it gets removed?
The original issue (2854) was open in 2009, 7 years later the "editable=false" is still deprecated and there isn't any valid XML alternative to it.
As of as Android-N Dev Preview 2 the best way to achieve the expected result is to set the EditText to android:editable="false".
Is this going to have a valid alternative or should I use android:editable until it gets removed?
de...@gmail.com <de...@gmail.com> #4
ch...@gmail.com <ch...@gmail.com> #5
Tired looking a solution for that..
As many programming language APIs available this should not be deprecated, or there should be a valid alternative.
As many programming language APIs available this should not be deprecated, or there should be a valid alternative.
da...@gmail.com <da...@gmail.com> #6
Why is this bug ignored?!?
Are we supposed to keep using the deprecated editable="false"?
This bug is open since 2009, it's been 7 years now. (this is a reopen of an automatically closed bug).
It is assigned but now one is looking into it.
Are we supposed to keep using the deprecated editable="false"?
This bug is open since 2009, it's been 7 years now. (this is a reopen of an automatically closed bug).
It is assigned but now one is looking into it.
ro...@google.com <ro...@google.com>
yh...@gmail.com <yh...@gmail.com> #7
I am waiting for the fix, too. I hope it will be fixed soon.
si...@google.com <si...@google.com>
ju...@gmail.com <ju...@gmail.com> #8
Any updates on this one?
al...@gmail.com <al...@gmail.com> #9
Still waiting...
si...@gmail.com <si...@gmail.com> #10
All Clears and new update
fu...@gmail.com <fu...@gmail.com> #11
Any new update?
su...@gmail.com <su...@gmail.com> #12
Any new update?
[Deleted User] <[Deleted User]> #13
hm any updates?
ez...@gmail.com <ez...@gmail.com> #14
please fix this bug, since android:editable="false" still marked as deprecated..
sa...@google.com <sa...@google.com> #15
Thank you for the feedback. We're closing this issue as Obsolete.
If it is still observed in the latest Android release, please open a new issue inhttps://goo.gl/TbMiIO along with a reference to this issue.
If it is still observed in the latest Android release, please open a new issue in
ma...@gmail.com <ma...@gmail.com> #17
Is google jsut going to ignore this bug?
Description
the documentation for it say:
"Use inputType instead."
but inputType="none" does not achieve anything, there's no inputType that makes EditText work as if using editable="false"
Why would you do it?
I just give you an example
I want to wrap my EditText for birthday with the new design library widget:
android.support.design.widget.TextInputLayout
this widget does not work on non-EditText.
I still want to lock the EditText so that the user does not manually change the value but has to go throw my button that open a Date Picker.
disabling the EditText visually change the widget and even if I can redefine the background / text color it's just way easier to just set editable="false"
I suggest to either remove the deprecation or introduce a new inputType="lock" that does the thing editable="false" did.
This way we can both set editable="false" (older platforms) and inputType="lock" (new ones).
This bug is a re-opening of very old bug marked as obsolete but never solved:
Bonus: setting lock / editable="false" should trigger a warning if focusable has not been set to false too to avoid the issue described in