Chrome's XSS Auditor sometimes complains about code included in widgets (e.g. Instangram, Twitter) embedded in WYSIWYG fields using this module. Whereas the widget code is not malicious, Chrome perceives it as such and throws the error, "err_blocked_by_xss_auditor", which doesn't allow the node to be saved / previewed.
This can be solved by sending the X-XSS-Protection header on node edit pages where the WYSIWYG context is also present.
This is not necessarily a bug of this module but a feature request, as it'd be nice to give users the ability to turn the header on and off depending on their preference / circumstances.
Comments
Comment #2
ioanmar commentedComment #3
ioanmar commentedUploading an updated version of the patch that checks for the existence of the wysiwyg_widget plugin instead of node related actions.
Comment #5
tashaharrison80 commentedTested and works as described.
Comment #6
tashaharrison80 commentedComment #7
tashaharrison80 commented