Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   Strange browser behaviour with chrome?, posted by Tim Schel on Mon Mar 30 14:46:28 2015 2015-03-30_14_25_52-ELOG_Amadou.png2015-03-30_14_25_32-ELOG_Kandidaten.png
    icon2.gif   Re: Strange browser behaviour with chrome?, posted by Stefan Ritt on Mon Mar 30 17:48:06 2015 
       icon2.gif   Re: Strange browser behaviour with chrome?, posted by Andreas Luedeke on Tue Mar 31 11:36:25 2015 
          icon2.gif   Re: Strange browser behaviour with chrome?, posted by Stefan Ritt on Tue Mar 31 11:44:27 2015 
             icon2.gif   Re: Strange browser behaviour with chrome?, posted by Andreas Luedeke on Wed Apr 1 10:54:27 2015 
                icon2.gif   Re: Strange browser behaviour with chrome?, posted by Stefan Ritt on Wed Apr 1 11:41:31 2015 
                   icon2.gif   Re: Strange browser behaviour with chrome?, posted by Andreas Luedeke on Wed Apr 1 18:31:28 2015 
                      icon2.gif   Re: Strange browser behaviour with chrome?, posted by Andreas Luedeke on Wed Apr 1 18:39:14 2015 
                      icon2.gif   Re: Strange browser behaviour with chrome? </table>, posted by Stefan Ritt on Wed Apr 1 20:25:21 2015 
          icon2.gif   Re: Strange browser behaviour with chrome?, posted by Tim Schelfhout on Wed Apr 1 11:01:14 2015 
Message ID: 67854     Entry time: Wed Apr 1 20:25:21 2015     In reply to: 67852
Icon: Reply  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Question  OS: Windows  ELOG Version: ELOG V2.9. 
Subject: Re: Strange browser behaviour with chrome? </table> 

Andreas Luedeke wrote:
Now I'm confused: if I create an entry with "elog -n 2 ...", then I put HTML code into elog and it is displayed as HTML. This HTML code does NOT convert a "<" into "&lt;", otherwise you could not display any HTML.
But of course this code can be wrongly formatted, for example it can contain a </table> tag without a <table> tag before it. This will definitely spoil the display in ELOG, and that was what I was refering to.
I agree that html tags in plain text entries will not have this problem.


Sure, in the main body text you can insert arbitrary HTML if this type of encoding is not prohibited. The &lt; encoding I meant was for attribute values. Proof of principe above in the Subject field.
ELOG V3.1.5-fe60aaf