W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > November 2009

[Bug 8238] Add support for X3D

From: <bugzilla@wiggum.w3.org>
Date: Sun, 08 Nov 2009 10:28:56 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1N750y-0002Qx-T1@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8238





--- Comment #3 from Sam Ruby <rubys@intertwingly.net>  2009-11-08 10:28:56 ---
(In reply to comment #2)
> It would be helpful to convert this bug report to a more specific request.

Maciej, can you explain what you perceive to be missing?

Meanwhile, I'll restate the request as follows: the request is for embedded X3D
grammars to be parsed into the DOM in a way that matches what is produced when
the same grammar is included in XHTML.

As background, the current spec causes the parser to go into a different mode
when an element whose name matches "math" or "svg" is encountered.  This
affects the namespace of the associated and nested elements, causes trailing
solidus characters in start element tag syntax to be interpreted as void
elements, and causes a number of element and attribute names to be fixed up to
be mixed case.  Doing the same for X3D would address this request.

The referenced email describes an alternate approach which would work for all
elements but the "i18n" element in X3D.  It would not recover properly from
cases where a non-well-formed X3D fragment is included in a larger document
which consists of HTML elements in ALL CAPS (something that is conforming, but
increasingly rare), but at least all conforming HTML5 parsers would recover
consistently.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Sunday, 8 November 2009 10:29:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:05 UTC