ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67847
|
Wed Apr 1 11:01:14 2015 |
 | Tim Schelfhout | tim.schelfhout@fixbrussel.be | Question | Windows | ELOG V2.9. | Re: Strange browser behaviour with chrome? |
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??
Chrome version is 41.0.2272.101
Don't know why ??? ... tried disabling all of the added extensions in chrome but to no avail.
Don't know what else can be different in both modes.
| Andreas Luedeke wrote: |
| Stefan Ritt wrote: | The (correct) display tells me that the colours are user-defined, probably by the configuration option
Style <attribute> <value> = <style>
which selects different styles for different rows. Now I do not know why your browser should change behaviour all over sudden, but I would double check the configuration. Like removing all style additions in the config file, then try again, then add one by one. There could also be a class defined with the "style" option which has not been added to the default style file themes directory of the elog installation.
Stefan |
Just my two cent:
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.
You could try to select the very same entries in both browsers, to see if it does depend on the specific entry content.
If the problem persists, then I would suggest that you post the following:
- a minimal configuration for a logbook that reproduces the problem; and
- the actual entries, exported in XML or RAW format; and
- screenshots on how it displays with IE (add version number) and with Chrome (add version number).
Cheers
Andreas |
|
|
67846
|
Wed Apr 1 10:54:27 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | ELOG V2.9. | Re: Strange browser behaviour with chrome? |
| Stefan Ritt wrote: |
| 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 |
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. |
|
67845
|
Tue Mar 31 11:44:27 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | ELOG V2.9. | 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 |
|
67844
|
Tue Mar 31 11:36:25 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | ELOG V2.9. | Re: Strange browser behaviour with chrome? |
| Stefan Ritt wrote: | The (correct) display tells me that the colours are user-defined, probably by the configuration option
Style <attribute> <value> = <style>
which selects different styles for different rows. Now I do not know why your browser should change behaviour all over sudden, but I would double check the configuration. Like removing all style additions in the config file, then try again, then add one by one. There could also be a class defined with the "style" option which has not been added to the default style file themes directory of the elog installation.
Stefan |
Just my two cent:
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.
You could try to select the very same entries in both browsers, to see if it does depend on the specific entry content.
If the problem persists, then I would suggest that you post the following:
- a minimal configuration for a logbook that reproduces the problem; and
- the actual entries, exported in XML or RAW format; and
- screenshots on how it displays with IE (add version number) and with Chrome (add version number).
Cheers
Andreas |
|
67843
|
Mon Mar 30 17:48:06 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | ELOG V2.9. | Re: Strange browser behaviour with chrome? |
The (correct) display tells me that the colours are user-defined, probably by the configuration option
Style <attribute> <value> = <style>
which selects different styles for different rows. Now I do not know why your browser should change behaviour all over sudden, but I would double check the configuration. Like removing all style additions in the config file, then try again, then add one by one. There could also be a class defined with the "style" option which has not been added to the default style file themes directory of the elog installation.
Stefan |
|
67842
|
Mon Mar 30 14:46:28 2015 |
 | Tim Schel | tim.schelfhout@fixbrussel.be | Question | Windows | ELOG V2.9. | Strange browser behaviour with chrome? |
Hello there,
I have been using ELOG for 4 years now and all of a sudden I see a strange behaviour.
As you can see in the screenshots below I have configured 6 logbooks (tabs) ... only 2
display (colors in CSS?) correctly as configured.
There haven't been any changes recently configuration wise .. but I suspect my chrome
has been upgraded silently.
Any ideas why one logbook (see screenshot 2) called Kandidaten would display
correctly and the other called DSP doesn't?
The first screenshot displays all rows in blue and purple letters ....
The Logbook Stagiairs even has multiple behaviours .... some of it sub books display correctly
and some don't.
I have a new colleague since a few days who uses the ELOG as well but using Internet Explorer
and she doesn't have this strange behaviour. I can rule out configuration error since
I stripped configuration and added verbosity logging level up and nothing was detected.
Is this possible solely due to chrome update (of which I am not even sure).
I looked at the CSS source of both screenshots and I notice that in the first case (wrong!)
there is no CSS class attributed to the TD elements.
Anyway I can understand that the browser displays everything wrong ... but this behaviour
I cannot explain. |
| Attachment 1: 2015-03-30_14_25_52-ELOG_Amadou.png
|
|
| Attachment 2: 2015-03-30_14_25_32-ELOG_Kandidaten.png
|
|
|
67841
|
Fri Mar 27 08:24:47 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 3.0.0 | Re: Permission to view |
No.
| Banata Wachid Ridwan wrote: |
|
so if that is the solution, all user that not allowed cannot login and cannot fill logbook
in my case, user still can login and fill logbook but cannot see other user's data on the same logbook, so user only see their own data.
but few members have a special permission to see all.
is that possible?
| Stefan Ritt wrote: |
|
You need
Password file = logbook.pwd
Login user = <name of allowed user(s)>
|
|
|
|
67840
|
Fri Mar 27 08:19:56 2015 |
| Banata Wachid Ridwan | jogjacard@yahoo.com | Question | Windows | 3.0.0 | Re: Permission to view |
so if that is the solution, all user that not allowed cannot login and cannot fill logbook
in my case, user still can login and fill logbook but cannot see other user's data on the same logbook, so user only see their own data.
but few members have a special permission to see all.
is that possible?
| Stefan Ritt wrote: |
|
You need
Password file = logbook.pwd
Login user = <name of allowed user(s)>
|
|