W3C home > Mailing lists > Public > www-svg@w3.org > February 2006

RE: [SVGMobile12] Processing model for unknown elements

From: Jon Ferraiolo <jonf@adobe.com>
Date: Sat, 4 Feb 2006 07:11:30 -0800
Message-ID: <6ECA24BE410D994496A2AE995367C5C86B9132@namail3.corp.adobe.com>
To: "Cameron McCormack" <cam-www-svg@aka.mcc.id.au>, <www-svg@w3.org>

Yes, Cameron, your suspicion is correct. We need to improve the wording
of the spec in this area.

Jon Ferraiolo
Adobe Systems, Inc.
Member SVG Working Group

-----Original Message-----
From: www-svg-request@w3.org [mailto:www-svg-request@w3.org] On Behalf
Of Cameron McCormack
Sent: Friday, February 03, 2006 6:39 PM
To: www-svg@w3.org
Subject: [SVGMobile12] Processing model for unknown elements

Hi WG.

In SVG Tiny 1.2 it currently states[1]:

  Within an SVG document fragment, unknown elements, including unknown
  elements in the SVG or XML Events namespaces as well as known elements
  in the SVG or XML Events namespaces occuring in unexpected locations,
  and their descendant elements do not participate in SVG rendering and
  are not processed beyond their contribution to the construction of the
  DOM. The processing model for unknown elements is equivalent to an
  <svg:g> element with the 'display' property set to 'none'.

I think it should be made clear what the "processing model" here means.
Does it mean that the unknown elements have DOM objects that implement
SVGLocatableElement, since that is what 'g' elements have?  Or just that
the rendering model is the same as for a "display: none"ed group (which
is what I suspect)?



[1] http://www.w3.org/TR/SVGMobile12/implnote.html#UnsupportedProps

 Cameron McCormack			ICQ: 26955922
 cam (at) mcc.id.au			MSN: cam (at) mcc.id.au
 http://mcc.id.au/			JBR: heycam (at) jabber.org
Received on Saturday, 4 February 2006 15:13:08 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:07 UTC