- From: Rick <graham.rick@gmail.com>
- Date: Tue, 12 Mar 2013 08:59:30 -0400
- To: www-svg <www-svg@w3.org>
- Message-ID: <CAGDjS3cdj6Gq37-pSprYtuQ9OZGTF4RXu2p6E9Wxerea5SE2pA@mail.gmail.com>
On Mon, Mar 11, 2013 at 3:27 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > On 3/11/13 10:53 AM, Robin Berjon wrote: > > I'm not saying that SVG is HTML >> > > You are if you're saying that every SVGElement is an HTMLElement.... ;) And that would be an ugly mistake. > > > but at the very least in a browser >> context, even when standalone, it really should script in the same way. >> > > Does that include all the DOM properties that just reflect content > attributes, especially if those content attributes don't make sense for SVG? > > It seems to me like the right way to handle SVG and HTML wanting to share > some DOM bits that really don't belong on Element for whatever reason is to > factor out all those bits onto an separate interface that both HTMLElement > and SVGElement implement... > If this can be done, it seems the best solution. > > -Boris > > -- Diplomacy is the art of saying "nice doggy" until you can find a rock. -- Diplomacy is the art of saying "nice doggy" until you can find a rock.
Received on Tuesday, 12 March 2013 13:00:06 UTC