Re: Strange browser behaviour with chrome?, posted by Stefan Ritt on Mon Mar 30 17:48:06 2015
|
The (correct) display tells me that the colours are user-defined, probably by the configuration option
Style <attribute> <value> = <style>
|
|
Re: Strange browser behaviour with chrome?, posted by Andreas Luedeke on Tue Mar 31 11:36:25 2015
|
[quote="Stefan Ritt"]The (correct) display tells me that the colours are user-defined, probably by the configuration option
Style <attribute> <value> = <style>
|
|
Re: Strange browser behaviour with chrome?, posted by Stefan Ritt on Tue Mar 31 11:44:27 2015
|
[quote="Andreas Luedeke"]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.[/quote]
|
|
Re: Strange browser behaviour with chrome?, posted by Andreas Luedeke on Wed Apr 1 10:54:27 2015
|
[quote="Stefan Ritt"][quote="Andreas Luedeke"]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.[/quote]
|
|
Re: Strange browser behaviour with chrome?, posted by Tim Schelfhout on Wed Apr 1 11:01:14 2015
|
Thank you all of you for your notes ...
Anyway I have no time at the present to debug this ... at the level of configuration file.
I discovered however that the Incognito Mode of Chrome does NOT seem to have this problem??
|
|
Re: Strange browser behaviour with chrome?, posted by Stefan Ritt on Wed Apr 1 11:41:31 2015
|
[quote="Andreas Luedeke"]If the content has been added with the "elog" command as HTML then it can contain mismatching HTML tags, can't it?
I don't see how this could be avoided by ELOG, unless you want to do a full HTML syntax check of all new and modified entries.[/quote]
|
|
Re: Strange browser behaviour with chrome?, posted by Andreas Luedeke on Wed Apr 1 18:31:28 2015
|
[quote="Stefan Ritt"][quote="Andreas Luedeke"]If the content has been added with the "elog" command as HTML then it can contain mismatching HTML tags, can't
it?
I don't see how this could be avoided by ELOG, unless you want to do a full HTML syntax check of all new and modified entries.[/quote]
|
|
Re: Strange browser behaviour with chrome?, posted by Andreas Luedeke on Wed Apr 1 18:39:14 2015
|
Proof of principle ;-) |