20579 2013-01-06 16:46:10 +0000 Should entering designMode disable scripting for the document? 2013-03-14 00:36:28 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED WORKSFORME http://www.whatwg.org/specs/web-apps/current-work/#making-entire-documents-editable:-the-designmode-idl-attribute P3 normal Unsorted 1 contributor ian ap ayg bzbarsky ehsan ian james mike ojan rniwa travil w3c contributor oldest_to_newest 80961 0 contributor 2013-01-06 16:46:10 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/editing.html Multipage: http://www.whatwg.org/C#making-entire-documents-editable:-the-designmode-idl-attribute Complete: http://www.whatwg.org/c#making-entire-documents-editable:-the-designmode-idl-attribute Comment: Should entering designMode disable scripting for the document? Posted from: 173.48.81.109 by bzbarsky@mit.edu User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:20.0) Gecko/20121217 Firefox/20.0 80962 1 bzbarsky 2013-01-06 16:47:12 +0000 This testcase: <!DOCTYPE html> <body onclick="alert('hey there')"> Click me: do I alert? <script> document.designMode = "on"; </script> <script> alert('Hey, I still run'); </script> </body> suggests non-WebKit UAs disable scripting in designmode: neither the second <script> nor the click handler run in IE9, Gecko, or Presto. 81113 2 ayg 2013-01-09 12:17:43 +0000 For reference, my thoughts on the matter from some time ago: https://bugzilla.mozilla.org/show_bug.cgi?id=765780#c7 http://lists.w3.org/Archives/Public/public-html/2011Jul/0069.html If you decide to go like non-WebKit browsers and disable scripting, make sure to specify whether the current script runs to completion or not when designMode is turned on. IE doesn't, last I checked (IE9) -- if you do <script> document.designMode = "on"; alert('First alert'); </script> <script> alert('Second alert'); </script> then WebKit alerts both, Gecko/Opera only alert the first, and IE alerts neither. 84089 3 ian 2013-03-07 22:58:33 +0000 Since there's no complete interop here, I'm very very sorely tempted to leave it as is (so in this case, matching WebKit, allowing script). It has the additional benefit of being the simplest of the options. But I'm certainly eager to entertain the alternatives, especially since not running script is more common, even if it is done differently in different browsers. Is anyone aware of compat needs one way or the other? 84281 4 bzbarsky 2013-03-12 02:20:35 +0000 Note that I'm contemplating changing the Gecko behavior to match WebKit here. 84363 5 travil 2013-03-13 20:01:11 +0000 FWIW, IE is also contemplating moving to not disabling scripting in designMode (more closely matches contenteditable). 84381 6 ian 2013-03-14 00:36:28 +0000 Alright. I'm marking this WORKSFORME for now then. Please reopen if either of you decide otherwise, ideally explaining why in a way that might convince the other browser vendors to agree with you. :-)