- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Sat, 9 Feb 2013 12:05:36 +1300
- To: Rik Cabanier <cabanier@gmail.com>
- Cc: Cameron McCormack <cam@mcc.id.au>, "www-svg@w3.org" <www-svg@w3.org>
- Message-ID: <CAOp6jLbsPdL5L61Nx46ZSuzQ381pvCaTDT=m6q9XO2ZtMfon-g@mail.gmail.com>
On Sat, Feb 9, 2013 at 11:01 AM, Rik Cabanier <cabanier@gmail.com> wrote: > On Sat, Feb 9, 2013 at 8:44 AM, Robert O'Callahan <robert@ocallahan.org>wrote: > >> I think we should allow foreignObject. Web renderers can handle it. I >> think there's a high chance at some point we'll allow including HTML in SVG >> without foreignObject at which point preventing that in fonts or images >> will become more difficult. Generally as SVG and HTML converge preventing >> foreignObject will become less relevant. >> >> Yes, if that happens, it should be allowed. > > Will this require changes to the HTML parser? (ie all external references > such as script blocks should be disallowed) Would the HTML content reflow > when the glyph is resized? > A SVG glyphs document is always parsed as XML so the HTML parser never gets called. Script is disabled not by modifying the parser or DOM, but by just not running script --- this is already specced out. There's no resizing of the SVG glyphs document or any of its contents, except for stuff triggered by animation. > Also, my fear is that people will abuse it and just make HTML characters. > I can't imagine why anyone would want to do that, and it wouldn't be that bad if they did. Rob -- Wrfhf pnyyrq gurz gbtrgure naq fnvq, “Lbh xabj gung gur ehyref bs gur Tragvyrf ybeq vg bire gurz, naq gurve uvtu bssvpvnyf rkrepvfr nhgubevgl bire gurz. Abg fb jvgu lbh. Vafgrnq, jubrire jnagf gb orpbzr terng nzbat lbh zhfg or lbhe freinag, naq jubrire jnagf gb or svefg zhfg or lbhe fynir — whfg nf gur Fba bs Zna qvq abg pbzr gb or freirq, ohg gb freir, naq gb tvir uvf yvsr nf n enafbz sbe znal.” [Znggurj 20:25-28]
Received on Friday, 8 February 2013 23:06:05 UTC