Perhaps the corect description should be.

Elements without textual content collapse their next element* into them.

This would cause to collapase element "body" into element "link" or
"script" of element "head"; which means that the resulted document
would not be usable.

* The word element is intentionally singular; as in, "an element".

Schimon

On Sun, 24 Aug 2025 13:06:42 +0300
Schimon Jehudah via lxml - The Python XML Toolkit <lxml@python.org>
wrote:

> Good day.
> 
> Previous subject: [lxml] Re: A possible problem with processing of
> XSLT
> 
> I think, that I have found the cause to the issue, or, at least, now I
> know how to cause to the issue, and how to define it.
> 
> 
> Issue
> -----
> 
> Elements without text content would overlap.
> 
> 
> Samples to experiment with
> --------------------------
> 
> <nav id="xslt-navigation-posts">
>   <span id="xslt-navigation-previous"/>
>   <span id="xslt-navigation-proceed"/>
> </nav>
> 
> <nav id="xslt-navigation-posts">
>   <span id="xslt-navigation-previous"></span>
>   <span id="xslt-navigation-proceed"></span>
> </nav>
> 
> 
> Result after processing
> -----------------------
> 
> <nav id="xslt-navigation-posts">
>       <span id="xslt-navigation-previous">
>       <span id="xslt-navigation-proceed">
>     </span></span></nav>
> 
> 
> Severness
> ---------
> 
> The severness is high, because this would affect on embedding of
> CSS stylesheets and ECMAScript scripts and other elements that do not
> require or should not have textual content.
> 
> Examples:
> 
> <script src="/scripts/navigation.js" type="text/javascript"></script>
> 
> <script src="/scripts/navigation.js" type="text/javascript" />
> 
> 
> Note
> ----
> 
> This issue does not occur with client-side XSLT parsers of internet
> browsers such as Falkon and Otter Browser.
> 
> 
> Kind regagrds,
> Schimon
> 
> On Thu, 21 Aug 2025 20:57:28 +0300
> Schimon Jehudah via lxml - The Python XML Toolkit <lxml@python.org>
> wrote:
> 
> > Good evening.
> > 
> > It appears that this issue is easy to reproduce and probably is easy
> > to fix as well.
> > 
> > I would appreciate someone ot assist in writing and report about
> > that issue.
> > 
> > Kind regards,
> > Schimon
> > 
> > On Fri, 25 Jul 2025 19:13:58 +0300
> > Schimon Jehudah via lxml - The Python XML Toolkit <lxml@python.org>
> > wrote:
> >   
> > > Good evening.
> > > 
> > > I am manipulating XSLT files with LXML.
> > > 
> > > Much of it works well.
> > > 
> > > Yet, it appears, that there is an issue with LXML, or libxml2, or
> > > libxslt upon rare circumstances which I am not sure that I am
> > > eloquent enough to explain.
> > > 
> > > I would appreciate help in analyzing this possible issue, if this
> > > is indeed a genuine issue.
> > > 
> > > I have detailed and linked to the relevant code.
> > > 
> > > https://git.xmpp-it.net/sch/Rivista/issues/6
> > > 
> > > Please advise.
> > > 
> > > P.S. I will be available during Saturday or Sunday evening.
> > > 
> > > Kind regards,
> > > Schimon
> > > _______________________________________________
> > > lxml - The Python XML Toolkit mailing list -- lxml@python.org
> > > To unsubscribe send an email to lxml-le...@python.org
> > > https://mail.python.org/mailman3//lists/lxml.python.org
> > > Member address: sch@fedora.email    
> > _______________________________________________
> > lxml - The Python XML Toolkit mailing list -- lxml@python.org
> > To unsubscribe send an email to lxml-le...@python.org
> > https://mail.python.org/mailman3//lists/lxml.python.org
> > Member address: sch@fedora.email  
> _______________________________________________
> lxml - The Python XML Toolkit mailing list -- lxml@python.org
> To unsubscribe send an email to lxml-le...@python.org
> https://mail.python.org/mailman3//lists/lxml.python.org
> Member address: sch@fedora.email
_______________________________________________
lxml - The Python XML Toolkit mailing list -- lxml@python.org
To unsubscribe send an email to lxml-le...@python.org
https://mail.python.org/mailman3//lists/lxml.python.org
Member address: arch...@mail-archive.com

Reply via email to