W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2012

Re: [whatwg] Including HTML more directly into SVG

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 11 Sep 2012 09:10:07 -0700
Message-ID: <CAAWBYDBYJQM91Vr8Pg5y0jW-EedcTa6FPQz9PQrwjVXqFyRy+Q@mail.gmail.com>
To: Elliott Sprehn <esprehn@gmail.com>
Cc: WHATWG <whatwg@whatwg.org>
On Tue, Sep 11, 2012 at 1:23 AM, Elliott Sprehn <esprehn@gmail.com> wrote:
> On Tue, Sep 11, 2012 at 1:15 AM, Elliott Sprehn <esprehn@gmail.com> wrote:
>> On Mon, Sep 10, 2012 at 4:59 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
>>
>>...
>>>
>>> Another solution could be SVG inventing their own elements for these
>>> kinds of things.  For example, #1 could be solved with an <svg:span>
>>> or <svg:p> element.  Having duplicate elements in multiple namespaces
>>> is regarded as an antipattern, ...
>>
>> SVG has a totally different font and styling model, different kinds of
>> animations, filters, etc. The paragraph and span concept in SVG
>> wouldn't be the same thing so it's not an antipattern. You would have
>> to specify some kind of x/y coordinate and the width since SVG doesn't
>> have a flow concept so there would be nothing to size or place
>> against.
>>
>
> See also http://www.w3.org/TR/2004/WD-SVG12-20041027/flow.html

There is a reason why nobody implemented 1.2.  Reinventing inline
layout with a subtly different model is one of them.

~TJ
Received on Tuesday, 11 September 2012 16:11:11 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:45 UTC