Re: [whatwg] Should scripts and plugins in contenteditable content be enabled or disabled?

2010-07-29 Thread Ian Hickson
On Fri, 23 Apr 2010, Simon Pieters wrote: On Fri, 23 Apr 2010 01:28:47 +0200, Robert O'Callahan wrote: See https://bugzilla.mozilla.org/show_bug.cgi?id=519928 Suppose we have a script element inside a contenteditable parent. Should the script run? What about on* attribute event

Re: [whatwg] Should scripts and plugins in contenteditable content be enabled or disabled?

2010-05-21 Thread Perry Smith
On May 19, 2010, at 8:14 PM, Collin Jackson wrote: On Wed, May 19, 2010 at 4:57 PM, Adam Barth w...@adambarth.com wrote: Virtually none of the JavaScript framebusting scripts used by web sites are effective. Yes. If anyone would like to see more evidence of this, here's a recent study of

Re: [whatwg] Should scripts and plugins in contenteditable content be enabled or disabled?

2010-05-19 Thread Robert O'Callahan
On Wed, May 19, 2010 at 5:35 AM, Ojan Vafai o...@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

Re: [whatwg] Should scripts and plugins in contenteditable content be enabled or disabled?

2010-05-19 Thread Adam Barth
On Wed, May 19, 2010 at 4:32 PM, Robert O'Callahan rob...@ocallahan.org wrote: On Wed, May 19, 2010 at 5:35 AM, Ojan Vafai o...@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

Re: [whatwg] Should scripts and plugins in contenteditable content be enabled or disabled?

2010-05-19 Thread Collin Jackson
On Wed, May 19, 2010 at 4:57 PM, Adam Barth w...@adambarth.com wrote: Virtually none of the JavaScript framebusting scripts used by web sites are effective. Yes. If anyone would like to see more evidence of this, here's a recent study of the Alexa Top 500 web sites. None of them were

Re: [whatwg] Should scripts and plugins in contenteditable content be enabled or disabled?

2010-05-18 Thread Ojan Vafai
On Fri, Apr 23, 2010 at 2:34 AM, Robert O'Callahan rob...@ocallahan.orgwrote: On Fri, Apr 23, 2010 at 6:52 PM, Simon Pieters sim...@opera.com wrote: It seems Hixie has decided to go back to the WebKit behavior in the spec for designMode.

Re: [whatwg] Should scripts and plugins in contenteditable content be enabled or disabled?

2010-05-18 Thread Robert O'Callahan
On Wed, May 19, 2010 at 5:35 AM, Ojan Vafai o...@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

Re: [whatwg] Should scripts and plugins in contenteditable content be enabled or disabled?

2010-04-23 Thread Simon Pieters
On Fri, 23 Apr 2010 01:28:47 +0200, Robert O'Callahan rob...@ocallahan.org wrote: See https://bugzilla.mozilla.org/show_bug.cgi?id=519928 Suppose we have a script element inside a contenteditable parent. Should the script run? What about on* attribute event handlers, should they fire in

[whatwg] Should scripts and plugins in contenteditable content be enabled or disabled?

2010-04-22 Thread Robert O'Callahan
See https://bugzilla.mozilla.org/show_bug.cgi?id=519928 Suppose we have a script element inside a contenteditable parent. Should the script run? What about on* attribute event handlers, should they fire in response to events? What about object plugins inside a contenteditable parent, should they