Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Summarization of http://drupal.org/node/81297 (actually copied from current wysiwyg.module):
Considerations:
- Take D6 FAPI3 / widgets into account (see #138706 and #86535).
- Run registration either in hook_elements() or hook_form_alter(). form_alter() might also allow to load needed JS/CSS.
- Use an attribute or class name or both (editor code analysis needed). Or alter field #type 'textarea' to 'html' (IIRC, suggested by Moshe in IRC).
- Disable an editor for fields using the PHP input format.
- D6: Perhaps depend on the input format to *enable* wysiwyg for a field.
- Allow to take the current path into account.
- Allow to force an editor for certain CCK fields (f.e. user input).
- Disable core's #resizable if an editor does not support it.
- Allow contrib modules to extend this definition.
- Allow to manually extend this list via wysiwyg settings page.
- Include an editor profile or user role to limit/enhance available plugins.
- Take other input formats (e.g. bbcode) into account.
Comments
Comment #1
sunMarking as duplicate of #253600: Attach client-side editors to input format enabled textareas only