10173 2010-07-15 14:16:17 +0000 Rendering of replaced content and foreign content 2010-10-04 13:57:47 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC All RESOLVED NEEDSINFO http://www.w3.org/2010/06/07-svg-minutes.html P2 normal LC 1 krisk ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 36919 0 krisk 2010-07-15 14:16:17 +0000 The spec should state as a MUST that for foreign content the default style comes from CSS2.1 spec and not the default style of the foreign content. For example, in a SVG document the root's default overflow == 'clipped' and for HTML the default for overflow == 'visible'. This was discussed and agreed upon to be correct by the SVG WG that the default for overflow should be 'visible', because when svg is in a HTML document it needs to follow CSS2.1 specification. http://www.w3.org/2010/06/07-svg-minutes.html By adding this it should help make SVG in html more interoperable w/o having web authors add svg { overflow: visible } to every HTML page that contains SVG. 37501 1 ian 2010-08-16 21:50:39 +0000 Are you saying the current spec is wrong (i.e. something needs changing) or are you saying it is insufficient (i.e. something needs adding)? 39026 2 krisk 2010-09-14 23:27:07 +0000 The spec is insufficient 39813 3 ian 2010-09-28 21:59:28 +0000 Sorry for being slow here. It's not clear to me what needs adding. What's the difference between the default style coming from CSS2.1 rather than the foreign content? I don't understand what either of those would mean. Isn't this just a matter of making sure the SVG UA style sheet makes sense for compound documents? Why is this an HTML issue and not an SVG issue? Does the problem not occur when SVG is mixed with other vocabularies? 40100 4 ian 2010-09-30 08:49:29 +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: Did Not Understand Request Change Description: no spec change Rationale: see comment 3