W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2013

Re: DOM 4 request

From: Richard Schwerdtfeger <schwer@us.ibm.com>
Date: Mon, 11 Mar 2013 08:18:19 -0500
To: Anne van Kesteren <annevk@annevk.nl>
Cc: annevankesteren@gmail.com, public-canvas-api@w3.org, www-dom@w3.org, www-svg@w3.org
Message-ID: <OF55042EFB.DF3FB86B-ON86257B2B.0047F878-86257B2B.00491681@us.ibm.com>



Rich Schwerdtfeger

annevankesteren@gmail.com wrote on 03/11/2013 06:21:28 AM:

> From: Anne van Kesteren <annevk@annevk.nl>
> To: Richard Schwerdtfeger/Austin/IBM@IBMUS,
> Cc: www-svg@w3.org, public-canvas-api@w3.org, www-dom@w3.org
> Date: 03/11/2013 06:22 AM
> Subject: Re: DOM 4 request
> Sent by: annevankesteren@gmail.com
>
> Resending with corrected addresses.
>
> On Mon, Mar 11, 2013 at 11:18 AM, Anne van Kesteren <annevk@annevk.nl>
wrote:
> >> Please let us know if the DOM working group would support adding this
> >> attribute [(activeElement)].
> >
> > It's already supported for SVG at the moment. HTML simply extends the
> > Document interface and does not create one specific for HTML. In terms

Hi Anne,

The issue is that SVG can run in standalone documents. For this reason we
have the following situation:

Here is the current Document object reference in SVG2:
Document element Interface:
https://svgwg.org/svg2-draft/struct.html#InterfaceSVGDocument

Here is the DOM4:
Document element Interface:
http://www.w3.org/TR/2012/WD-dom-20120405/#interface-document

Here is the HTML5
HTML5 Document element Interface:
http://www.w3.org/html/wg/drafts/html/CR/dom.html#the-document-object


> > of dependencies, HTML and DOM have a mutual dependency already (as
> > unfortunate as that may be). And actually, SVG must have a dependency
> > on HTML too for script scheduling and execution.
>
We agree that SVG has a huge dependency on HTML for scripting and
introducing tabindex to SVG2 has really brought a lot of these issues to
light in the SVG working group. Yet, the HTML5 Document object interface
has a lot of features that really don't apply in a standalone situation.
Here are a few

  readonly attribute HTMLCollection embeds;
  readonly attribute HTMLCollection plugins;
  readonly attribute HTMLCollection forms;

           attribute EventHandler onblur;   (SVG has a different handler
name for this - onfocusout)

So, are you suggesting that we simply take the HTML5 Document Object
interface and basically address the mapping issues like return null for
objects that have no applicability to SVG in a standalone environment?

If so, then we should also coordinate with the HTML WG and WhatWG on
ensuring clear specification of how this may be populated in the presence
of an SVG document in HTML. I am sure the browses have addressed a lot of
this but it has not been clearly spec'd to my knowledge.


Rich
>
> --
> http://annevankesteren.nl/
>
Received on Monday, 11 March 2013 13:19:01 GMT

This archive was generated by hypermail 2.3.1 : Monday, 11 March 2013 13:19:05 GMT