W3C home > Mailing lists > Public > www-svg@w3.org > November 2013

Re: Inline HTML

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 15 Nov 2013 12:36:27 -0800
Message-ID: <CAAWBYDA=G-ygSJOT3c=dOt7xjtcZMW+1bcwYfAaOH7hpeoBazw@mail.gmail.com>
To: Jelle Mulder <pjmulder@xs4all.nl>
Cc: www-svg <www-svg@w3.org>
On Fri, Nov 15, 2013 at 12:38 PM, Jelle Mulder <pjmulder@xs4all.nl> wrote:
> Thought
> If we cannot have nice new flow control <objects> in SVG as it would over
> complicate the language and we're working on using CSS to patch things up a
> bit.. Why not have Inline HTML? I can work the other way around with Inline
> SVG, so how about adding HTML code to be inline in SVG. I'd say that would
> solve quite some issues. It would also be vastly easier to maintain the
> standards and make sure things work in similar ways.
> I can just add whatever my fancy is from HTML and stick it into my SVG files
> rather than the other way around. I can keep my SVG nice and clean and don't
> have to bother creating a HTML framework just to get something to work, like
> it is now. <HTML> <DIV><DIV><DIV> </HTML> in my defs and low and behold, I
> have flow control, use CSS to get it at the right positions and using
> overflow and Z orders to make it do all the visual nice stuff.
> Most parsers can already handle both HTML and SVG and those that do not do
> SVG will not be breaking my code anyway. I guess it could be made useful in
> just a few iterations of browsers.

Yup, this is already the plan of record.  At minimum, we'd like to
allow the <html> element directly in SVG, with HTML inside of it.  We
might do a more complete merging and allow HTML elements like <p> to
just be inserted directly.

Received on Friday, 15 November 2013 20:37:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:54:47 UTC