That's clearly a bug. I'm looking at it now - the trick is getting Neko to identify the difference between:
<input disabled ...> and <input title=""> ... where the former should be rendered XML-wise as disabled="disabled", the latter as title="". On Wed, Mar 18, 2009 at 2:19 AM, Jordan Zimmerman <[email protected]> wrote: > The latest version of NekoSerializer.printStartElement() is outputting > empty attributes in a way that isn't XML compliant. i.e. given '<img > title=""/>' NekoSerializer will output '<img title/>'. This causes > Firefox's (I haven't tried others) DOM parser to throw an error. This is > coming up when using the OS templates framework. > > Thoughts? > > Jordan Zimmerman > Principal Software Architect > 831.647.4712 > 831.214.2990 (cell) > [email protected] > > SHOP*COMTM > Shop Smart, Save Big(tm) > www.shop.com > > > This message (including any attachments) is intended only for > the use of the individual or entity to which it is addressed and > may contain information that is non-public, proprietary, > privileged, confidential, and exempt from disclosure under > applicable law or may constitute as attorney work product. > If you are not the intended recipient, you are hereby notified > that any use, dissemination, distribution, or copying of this > communication is strictly prohibited. If you have received this > communication in error, notify us immediately by telephone and > (i) destroy this message if a facsimile or (ii) delete this > message > immediately if this is an electronic communication. > > Thank you. >
