[Bug 8238] Add support for X3D


--- Comment #6 from Sam Ruby <rubys@intertwingly.net>  2009-11-08 17:04:09 ---
(In reply to comment #4)
> With my browser implementor hat on, implementing a significant extra parsing
> complexity in browsers solely for a single feature that will only be
> implemented by script- or plugin-based add-ons does not seem like a good
> tradeoff.

Void elements pose a significant problem.  That data, once lost, is generally
impossible to reconstruct.

> If I understand correctly, the root element of X3D is not mixed case ("X3D"
> only has capital letters), so it doesn't seem like the email proposal satisfies
> your request. Interesting idea though.

I was imprecise.  I meant elements which contain at least one capital letter.

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 17:04:14 UTC