- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Fri, 13 Mar 2015 16:52:31 -0700
- To: Florian Rivoal <florian@rivoal.net>
- Cc: www-style list <www-style@w3.org>, Tantek Çelik <tantek@cs.stanford.edu>
On Fri, Mar 13, 2015 at 4:49 PM, Florian Rivoal <florian@rivoal.net> wrote: >> On 14 Mar 2015, at 00:22, Tab Atkins Jr. <jackalmage@gmail.com> wrote: >> On Fri, Mar 13, 2015 at 2:28 PM, Florian Rivoal <florian@rivoal.net> wrote: >>>> On 13 Mar 2015, at 22:14, Tab Atkins Jr. <jackalmage@gmail.com> wrote: >>>> On Fri, Mar 13, 2015 at 2:09 PM, Florian Rivoal <florian@rivoal.net> wrote: >>>>> As for external references in SVG, may or must not? >>>> >>>> That's already handled; external refs aren't allowed when invoked as a >>>> CSS image, as that uses the "secure static" or "secure animated" form. >>> >>> Cool, so that's settled. By the way, as long as we're handling animated (images, SVGs) as a should, we can probably put .cur as a should as well. >> >> Why? I thought you said everyone supports .cur; that implies we should MUST it. > > Sorry, I must have been tired when I wrote that. I meant .ani (the animated version of .cur). Ah, ok. Eh, I can take it or leave it. Supporting animation in a format that you already support animation in is different from supporting an additional file format just for animation purposes. I'd prefer we not mention it, probably, except maybe in a note. ~TJ
Received on Friday, 13 March 2015 23:53:17 UTC