Updates:
Cc: ja...@hoppipolla.co.uk
Comment #2 on issue 153 by geoffers: preserve order of attributes on
serialization
http://code.google.com/p/html5lib/issues/detail?id=153
There's no real way to fix this without relying upon
defined-to-be-undefined behaviour in CPython/lxml, and as such I'm
reluctant to do so. lxml says attributes are given in an arbitrary order,
and they are stored in a dict which CPython makes no guarantee of the order
of. (lxml does always insert attributes in document order into the dict,
and dicts are ordered by insertion order, so it does actually work… for
now, at least).
Yes, we could go against both the lxml/CPython documentation and rely upon
the ordering, but if either ever changes their behaviour, it could mean
html5lib could potentially start serializing the same lxml parse-tree in
random ways, and I'd much rather go for the definitely-consistent route we
have now.
--
You received this message because you are subscribed to the Google Groups
"html5lib-discuss" group.
To post to this group, send an email to html5lib-discuss@googlegroups.com.
To unsubscribe from this group, send email to
html5lib-discuss+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/html5lib-discuss?hl=en-GB.
