- From: <bugzilla@wiggum.w3.org>
- Date: Mon, 10 Mar 2008 04:32:44 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3771
jmdyck@ibiblio.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CLOSED |REOPENED
Resolution|FIXED |
------- Comment #6 from jmdyck@ibiblio.org 2008-03-10 04:32 -------
It occurs to me that this approach is unsound. For instance, consider:
element e { text {"foo"}, attribute a {"x"} }
The rules given in comment #1 or comment #2 will accept this and assign it a
static type, but we know that dynamically it will raise a type error, because
an attribute node follows a non-attribute node in the element constructor's
content sequence.
Received on Monday, 10 March 2008 04:32:51 UTC