Closed yamahito closed 2 years ago
Hey @yamahito :wave:,
Thank you for opening an issue. We will get back to you as soon as we can. Have you seen our Open Collective page? Please consider contributing financially to our project. This will help us involve more contributors and get to issues like yours faster.
https://opencollective.com/existdb
We offer
priority
support for all financial contributors. Don't forget to addpriority
label once you become one! :smile:
So if I choose 'direct output' in exide and inspect the result window, I see the list item as a first sibling rather than a surrounding li:
So, I suspect the exact nature of the bug was being obfusticated by browsers' HTML parsing, and the bug is actually that the element is duplicated as both parent and children.
🤦♂️ never mind, just spotted that http://exist-db.org/xquery/templates
should be http://exist-db.org/xquery/html-templating
Expected behaviour
@data-template="templates:each"
on an e.g.li
element produces oneli
for each member of a sequence given by@data-template-from
.Actual behaviour
An extra, superfluous, empty
li
element is inserted before (or sometimes around, see below) the expected results. Attributes are preserved.Reproduction steps
This is an old, established bug: see for example https://github.com/HistoryAtState/hsg-shell/issues/37.
In trying to replicate the behaviour I am seeing on our live server, I have instead managed to produce the superfluous
li
around the expected result, instead of before it; perhaps something to do with html vs xml outputs?:Please provide the following