You are viewing a wiki page. You are welcome to join the group and then edit it. Be bold!
In progress
- Filter options based on CSS attributes, not just HTML tags: Allow to configure HTML attributes in HTML filter to allow and/or strip only certain tag attributes.
See also all issues tagged with 'wysiwyg' and 'FilterSystemRevamp'.
Todo
- Limit available input formats by "type of widget" used (node type body, comment, block, etc)
- Bring consistency into how we apply formats and provide more format support where it is missing
- Add context for check_markup(): For example, Inline API needs context about the piece of content that is filtered. If a field in a node is filtered, the node should be passed to the filter, so inline macros can be expanded to display a file attachment download link for an upload attached to the passed in node. The same with users, comments, aso. so this is not limited to nodes.
Fixed
- Remove the teaser splitter: Yes, we can.
- Default input format per role and make access to filters first class permissions: Simplifies the input format configuration by moving input format access permissions to the regular user permissions form.
- Move custom help settings to blocks: Allows to control/add custom help blocks to arbitrary pages (including input format support like any other custom block).
- Text format widget: Redesign the input format widget.
- Allow behaviors to detach from AHAH/AJAX contents: Adds Drupal.detachBehaviors(), so (not only) Wysiwyg API can invoke editors to save contents back into form elements before a form is submitted via AJAX/AHAH.
- Textarea with input format attached: Allow Wysiwyg API to identify input format enabled textareas via the FAPI property #input_format.
- Make input formats reorderable
- Break out HTML escaping filter to make non-HTML input formats (instantly) recognizable
Categories: Issue lists