- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Sat, 9 Feb 2013 10:44:04 +1300
- To: Rik Cabanier <cabanier@gmail.com>
- Cc: Cameron McCormack <cam@mcc.id.au>, "www-svg@w3.org" <www-svg@w3.org>
Received on Friday, 8 February 2013 21:44:31 UTC
On Sat, Feb 9, 2013 at 1:42 AM, Rik Cabanier <cabanier@gmail.com> wrote: > I think everyone was in agreement that we don't want to limit the SVG > feature set or add features just for SVG OpenType fonts. > We can let it up to the user agent to gracefully degrade the experience if > they don't support a particular feature (ie video could just show the > poster frame). > > We were thinking of not allowing foreignObject since that can pull in HTML > and might be harder to control securily. > 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. 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 21:44:31 UTC