Both editable and non-editable text areas are really common use cases, and it’s a really simple attribute.
I’d like to make it as simple as possible to use in MXML without having to specify beads. Since the RichTextArea is not a simple wrapper on <textarea> anyway, I thought that adding an editable property is appropriate. I’m going to leave the simple TextArea without an editable property and it will always be editable by default Let’s discuss after I commit my changes. On Nov 8, 2016, at 6:19 PM, Alex Harui <aha...@adobe.com> wrote: > > > On 11/8/16, 8:05 AM, "Alex Harui" <aha...@adobe.com> wrote: > >> On 11/8/16, 2:39 AM, "Harbs" <harbs.li...@gmail.com> wrote: >> >>> It also feels like “editable" should be a first class citizen… > > Forgot to comment on this: Wouldn't folks typically change the visuals of > a non-editable control as well? If so, "editable" or "readOnly" should be > a bead and you can aggregate it into a higher-level TextArea, similar to > how we are handling disable. > > -Alex >
