- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 09 Jan 2007 22:56:13 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4151
hrennau@yahoo.de changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hrennau@yahoo.de
------- Comment #1 from hrennau@yahoo.de 2007-01-09 22:56 -------
Probably the only way out, but the implied restriction is a pity: a general
impossibility to incorporate detached namespace-sensitive attributes during
construction.
An alternative which comes to mind is probably unacceptable, but let me
nevertheless describe it: to accept the attribute without error IF the in-scope
namespaces of the receptor element include a namespace binding matching the
namespace binding implied by the QName/Notation value. Thus one could "prepare"
the receptor, if necessary. An obvious problem however would be that the
receptor's namespace bindings themselves are only finalized by analyzing the
attributes (3.7.4). Thus we would get an unpleasant mixture: some attributes
creating namespace bindings, and others requiring them.
Received on Tuesday, 9 January 2007 22:56:22 UTC