[whatwg] Should scripts and plugins in contenteditable content be enabled or disabled?
robert at ocallahan.org
Tue May 18 12:35:00 PDT 2010
On Wed, May 19, 2010 at 5:35 AM, Ojan Vafai <ojan at chromium.org> wrote:
> The webkit behavior of allowing all scripts makes the most sense to me. It
> should be possible to disable scripts, but that capability shouldn't be tied
> to editability. The clean solution for the CKEditor developer is to use a
> sandboxed iframe.
> I don't see a security benefit for disabling script as you'd have all the
> same issues with loading any user-content in a non-editable area. The only
> catch is that you *do* need to disable script from pasted and drag-dropped
> content (see http://trac.webkit.org/changeset/53442). Basically, any site
> serving user-content will already need to mitigate XSS some other way, so
> disabling script in editable areas is not necessary, but paste/drag-drop
> can't reasonably rely on server-side solutions, so must be done by the UA.
> Putting my developer hat on, trying to make Google Gadgets work in Google's
> rich text editor inside Firefox designMode was awful due to
> https://bugzilla.mozilla.org/show_bug.cgi?id=519928. A large percentage of
> tricks with turning off designMode, appending the iframe and turning
> designMode back on. It was an awful solution that never worked very well.
That makes sense to me. I'll see what the other editor developers think.
"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the whatwg