[4suite] Namespace bug in 4DOM (Pretty)Print ?
Alexandre Fayolle
alf at logilab.com
Tue Sep 19 11:30:45 MDT 2000
On Tue, 19 Sep 2000, Uche Ogbuji wrote:
> Bad idea. DOM L2 reluctantly allows mixing NS and non-NS code for
> strict backward compatability, but they point out that it's very bad
> practice to do so. If you're using NS functions, use _only_ NS
> functions. If you're using non-NS functions, use only non-NS
> functions. So you should either be using createElementNS above, or
> setAttribute. You shouldn't mix the forms within a single document.
> It's strictly correct, but you'll have some weird effects.
Point taken.
In another mail I have sent this afternoon on xml-sig, I was mentioning
accessing attributes created with setAttributeNS('',...) with
getAttribute(...). I had overseen the strict division between the NS
and the non-NS API. I strongly resent this (nothing on you, rather on the
W3C in general). I feel some very awkward choices were made in the XML
spec, and this causes very awkward backward compatibility issues that can
be felt in the API.
Well, we shall change all our createElement() calls to
createElementNS() calls. Thanks again
PS: I'm sorry to raise the Printer issues so late (relatively to your
release), but these are quite recent discoveries on our side. :o/
--
Alexandre Fayolle
http://www.logilab.com - "Mais o est donc Ornicar ?" -
LOGILAB, Paris (France).
More information about the 4suite
mailing list