W3C home > Mailing lists > Public > www-amaya@w3.org > July to September 2005

Re: Bug in Amaya 9

From: Laurent Carcone <laurent@w3.org>
Date: Wed, 31 Aug 2005 11:04:13 +0200
To: ivan@w3.org
Cc: www-amaya@w3.org
Message-Id: <20050831090413.DD27916DBE@tux.inrialpes.fr>

> 
>  
> > I have hit a strange bug with Amaya 9 (it is on Windows but I would not think it
> > is relevant).
> > 
> > I have an XHTML1.1 file with doctype and all the rest of it. However, I do one
> > more thing: I add some own attributes to my file. I do it in an XML proper
> > fashion, namely I use a namespace declaration in the <html> element and use the
> > namespace prefix.
> > 
> > I know it is not 100% kosher, because I do not add my internal DTD to the XHTML
> > DTD. In other words, from an DTD validity point of view it is not fully valid.
> > 
> > However, the reaction of Amaya 9 on this file is:
> > 
> > 	- it accepts it without any warning as a legal and valid XHTML file (does not
> > ask the usual question whether I want to see the errors, edit the invalid file,
> > etc). I can therefore edit the file in XHTML, everything looks perfect.
> > 	- however: it silently *removes all private attributes* from the file.
> > 
> > I think this behaviour is a bug.
> > 
> > [I use an XHTML file to create presentation slides, but the file is run through
> > a private XML processor partially controlled by those attributes...]
> > 
> > Ivan
> > 
> 
> Hello Ivan,
> 
> Indeed it seems to be a bug as the attributes in the scope of a 'private' 
> namespace shouldn't be removed.
> Can you send us (me) such a file so that I can more easily debug this problem ?

This bug is now fixed in cvs version. Amaya no longer removes the attributes 
of 'external' namespace.

Thanks,
Laurent Carcone
Received on Wednesday, 31 August 2005 10:05:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:30:48 UTC