Re: agenda, 30 April 2015 SVG WG telcon

Re Tab's agenda request:

> Agenda+: What if we just let SVG-in-HTML lowercase its names (rather
> than having to preserve the camel-case).  What are the
> downsides/compat risks?
>
>
I really don't think there is any problem with saying that SVG-in-HTML is
case insensitive as far as markdown parsing goes.  We are never going to
create element or attribute names that only differ by capitalization.
Authors would still be advised to use the standard capitalization for
maximum compatibility and ease of switching between inline and standalone
SVG.

The difficulty would probably come from some of the DOM methods.  Even for
SVG-in-HTML, you need to use .createElementNS() and related methods.  Those
are case sensitive, because they are based on XML.  Not sure how much of a
headache/performance impact it would be to add extra rules for using those
methods in HTML documents.

In contrast, with querySelector() and related methods, the same method is
either case sensitive or not depending on the type of element being
matched.  Which of course leads to the nasty bug in Blink/Webkit (where
they use case-sensitive matching but automatically lowercase the input
selector when in an HTML document, with the result that mixed case SVG
selectors never match anything).  Making all elements case
insensitive/automatically lowercased within an HTML doc would fix that bug,
but at the cost of complicating the other DOM methods.


Re:

> > * Blink’s intent to deprecate SMIL
> >
> https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/5o0yiO440LM
> >
>
> Noooooooooooo!!!!

I won't be on the call this week.  I trust that others can fill in the
detailed rant & rave about why CSS animations are not a substitute for
SMIL.