#2750 - More feedback and specificity for WYSIWYG Comcode scanning
| Identifier | #2750 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | More feedback and specificity for WYSIWYG Comcode scanning |
| Status | Open |
| Handling member | Deleted |
| Addon | core_rich_media |
| Description | The WYSIWYG text may be considered:
1) Pure HTML 2) Semi-HTML (i.e. will get scanned for Comcode) 3) Intended for lossy conversion to Comcode Currently it is automatic, except we currently allow case '3' to be disabled via a flag. We verge on '1' for maximum reliability if we detect there's no explicit Comcode to be scanned and either no links or at least one <a> tag in the markup already. Allow a flag to make it explicit how to handle it, and add a nice CKEditor toolbar item for managing that setting. If it is still set to automatic, add a little message along with the preview to say what choice was made and why. Particularly in the case of link parsing, as not having link parsing happening may confuse some people. |
| Steps to reproduce | |
| Additional information | Update "Link parsing" in tut_wysiwyg to reflect the change. |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".


Comments
There have been no comments yet