2750: More feedback and specificity for WYSIWYG Comcode scanning

ID	Project	Category	View Status	Date Submitted	Last Update

2750	Composr	core_rich_media	public	2016-07-30 16:08	2016-07-31 21:39

Reporter	Chris Graham	Assigned To
Priority	normal	Severity	feature
Status	new	Resolution	open

Summary	2750: More feedback and specificity for WYSIWYG Comcode scanning
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.
Additional Information	Update "Link parsing" in tut_wysiwyg to reflect the change.
Tags	No tags attached.
Attach Tags	(Separate by ",")

Time estimation (hours)	8
Sponsorship open

Date Added	Member	Amount Sponsored

View Status	Private (for security issues or disclosing of private information; if you submit as a guest, you will not be able to see your submission)
Note
Upload Files Maximum size: 32,768 KiB	Attach files by dragging & dropping, selecting or pasting them.
You are not logged in	You are not logged in. This means you will not get any e-mail notifications. And if you reply, we will not know for sure you are the original poster of the issue.

Date Modified	Username	Field
2016-07-30 16:08	Chris Graham	New Issue
2016-07-30 16:08	Chris Graham	Description Updated
2016-07-30 16:13	Chris Graham	Additional Information Updated