18148 2012-07-18 17:26:48 +0000 Please clarify if edit-ability inherits across <iframe seamless> and if we should respect iframe.contentDocument.designMode 2012-09-28 05:26:56 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#dom-iframe-seamless P3 normal --- 1 contributor silviapfeiffer1 eric mike public-html-admin public-html-wg-issue-tracking robin public-html-bugzilla oldest_to_newest 70762 0 contributor 2012-07-18 17:26:48 +0000 This was was cloned from bug 17015 as part of operation convergence. Originally filed: 2012-05-09 23:19:00 +0000 ================================================================================ #0 contributor@whatwg.org 2012-05-09 23:19:50 +0000 -------------------------------------------------------------------------------- Specification: http://www.whatwg.org/specs/web-apps/current-work/ Multipage: http://www.whatwg.org/C#dom-iframe-seamless Complete: http://www.whatwg.org/c#dom-iframe-seamless Comment: Please clarify if edit-ability inherits across <iframe seamless> and if we should respect iframe.contentDocument.designMode Posted from: 173.164.128.209 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_3) AppleWebKit/536.9 (KHTML, like Gecko) Chrome/20.0.1115.1 Safari/536.9 ================================================================================ #1 Eric Seidel 2012-05-09 23:23:16 +0000 -------------------------------------------------------------------------------- Currently we do respect iframe.contentDocument.designMode = "on" and do *not* inherit user-modify: http://css-infos.net/property/-webkit-user-modify This was discussed in https://bugs.webkit.org/show_bug.cgi?id=85940. ================================================================================ 74742 1 silviapfeiffer1 2012-09-28 05:26:56 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: applied patch https://github.com/w3c/html/commit/ce89b31106b627fdd0cea560e6885ecb13cf77a2 Rationale: adopted resolution by WHATWG