The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.This may be a per-editor issue, but I am not sure.
If I were to have an appropriately defined text area with 'disabled' #attribute added, then the text area would be disabled when the wysiwyg module is disabled.
When I enable the module, the gui text area is enabled when it should be disabled.
This is a request to somehow pass the initial #attibutes to the wysiwyg text area.
A use case might be with conditional fields where the text area is only enabled under certain conditions and is disabled by default.
Comments
Comment #1
twodFor references please see #disabled vs #attributes and the comment explaining the difference in includes/form.inc line 1871.
Wysiwyg currently disables editors completely when #disabled is used, see #659428: '#disabled' setting using FAPI is not respected.
Maybe we should trigger an editor's read-only mode (if it has one at all) when #attributes->disabled is set? However, we'd need a reliable way of being notified if the original textarea's disabled status changes, so we can change the editor's state accordingly (again, if the editor can't already handle this on its own).
Comment #2
sun