|
|
|
Demo
Discussion
|
|
Forum
Config Examples
Contributions
Vulnerabilities
|
| Discussion forum about ELOG |
Not logged in |
 |
|
|
Strange browser behaviour with chrome?, posted by Tim Schel on Mon Mar 30 14:46:28 2015 
|
Re: Strange browser behaviour with chrome?, posted by Stefan Ritt on Mon Mar 30 17:48:06 2015
| |
Re: Strange browser behaviour with chrome?, posted by Andreas Luedeke on Tue Mar 31 11:36:25 2015
| |
Re: Strange browser behaviour with chrome?, posted by Stefan Ritt on Tue Mar 31 11:44:27 2015
| |
Re: Strange browser behaviour with chrome?, posted by Andreas Luedeke on Wed Apr 1 10:54:27 2015
| |
Re: Strange browser behaviour with chrome?, posted by Stefan Ritt on Wed Apr 1 11:41:31 2015
| |
Re: Strange browser behaviour with chrome?, posted by Andreas Luedeke on Wed Apr 1 18:31:28 2015
| |
Re: Strange browser behaviour with chrome?, posted by Andreas Luedeke on Wed Apr 1 18:39:14 2015
| |
Re: Strange browser behaviour with chrome? </table>, posted by Stefan Ritt on Wed Apr 1 20:25:21 2015
| |
Re: Strange browser behaviour with chrome?, posted by Tim Schelfhout on Wed Apr 1 11:01:14 2015
|
|
|
Message ID: 67845
Entry time: Tue Mar 31 11:44:27 2015
In reply to: 67844
Reply to this: 67846
|
|
| Category: |
Question |
OS: |
Windows |
ELOG Version: |
ELOG V2.9. |
|
| Subject: |
Re: Strange browser behaviour with chrome? |
|
|
| Andreas Luedeke wrote: | | the content of a particular entry can change the rendering. If you have an HTML end tag like </table> or </font> in your entry, then the display after that entry may be spoiled. |
Actually not. If you have HTML statements in entries, they will be rendered using escape characters (like </table> -> </table>). This is necessary to avoid cross-side-script vulnerabilities (XSS). If this is not working in some case, let me know and I have to fix it. The only exception is if you explicitly allow this via Allow HTML = 1 |