W3C home > Mailing lists > Public > www-style@w3.org > July 2015

Re: [css-writing-modes][svg] Embedded SVG and inheritance

From: Koji Ishii <kojiishi@gmail.com>
Date: Mon, 27 Jul 2015 18:31:36 +0900
Cc: Leonard Rosenthol <lrosenth@adobe.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, fantasai <fantasai.lists@inkedblade.net>, Jonathan Kew <jfkthame@gmail.com>, "www-style@w3.org" <www-style@w3.org>, SVG WG <w3c-svg-wg@w3.org>, Brady Duga <duga@google.com>, www-svg <www-svg@w3.org>
Message-Id: <09BFF94F-378E-443B-B1E6-D9BC05A979DF@gmail.com>
To: Dirk Schulze <dschulze@adobe.com>

> On Jul 27, 2015, at 5:42 PM, Dirk Schulze <dschulze@adobe.com> wrote:
> 
>> On May 10, 2015, at 2:17 PM, Koji Ishii <kojiishi@gmail.com> wrote:
>> 
>> After learned a bit of SVG, I understand this issue is more
>> complicated than thought.
>> 
>> Amelia and Leonard suggested that SVG wants to inherit when SVG is
>> used to style text within HTML (e.g., decorative headings) cases.
>> fantasai and I had a mind that SVG when used as an image should not
>> inherit. I understand these are two separate use cases and desired
>> behavior vary.
> 
> In general an SVG image should be isolated from the context it is put in. This was a strong request that we got from security people in the past as well.
> 
> There is a proposal to relay certain values/information into a SVG document which can be referenced within the SVG document (similar to CSS custom properties just that the property is set by the context the SVG image gets embedded to). Jonathan Watt from Mozilla presented this proposal to the SVG WG at a F2F in London at some point. This is probably the opt-in way you are talking about?
> 
> However, in all other cases, the SVG context should be isolated from the host context for images. Both, SVG and HTML share the same context for inline SVG on the other hand. For iframe and embed it shouldn’t be any different than for HTML in an iframe.

Thank you Dirk. I wasn’t clearly thinking about the differences in the context, your words made it clear.

In short, I’m ok with what you said.

TL;DR; considering the differences in context, we have 3 cases:
1. External document
2. Inline, but author thinks it’s an embedded image (the example was this case)
3. Inline, decorative headings etc.

I have mild preference not to inherit in all 3 cases, because inheriting writing modes to a system that are not writing-mode-adaptive will simply break, and that was the original proposal. But inlining in vertical text should not be a major case that, if it requires special casing, I’m fine without it.

/koji
Received on Monday, 27 July 2015 09:32:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:52:18 UTC