Enhancements: option parity with textarea field

[nilshoerrmann]

When converting existing blueprints from textarea fields to the editor, I was expecting the plugin to respect the settings for files and uploads that are available for the textarea field: https://getkirby.com/docs/reference/panel/fields/textarea#file-upload-and-select

Comparing to other enhancements listed here on the issue tracker, I'd consider this one of the more important ones because it hinders us to update to the editor.

[nilshoerrmann]

Thinking about this, I'd say that for easing adoption of this plugin option parity with the textarea field (as far as possible and desireable) is very important.

[nilshoerrmann]

This includes things like minlength and maxlength (guessing this is complicated) and autofocus, default, counter, placeholder.

My guess is that disabled and required work out of the box – but I haven't tested yet.

[REHvision]

disabled: true technically works (no editing is possible but no visual difference)

translate: false technically works (no editing in secondary languages possible but no visual difference)

required: true doesn't work (the headline shows as required field but an empty editor can be saved - probably because of #80)

[bastianallgeier]

• [x] required: true
• [x] disabled: true
• [x] translate: false
• [ ] minlength:
• [ ] maxlength:
• [x] autofocus: true
• [x] default

[silllli]

I think adjusting the available buttons (that appear when selecting text) and disabling them should also be possible.