|
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: 67842
Entry time: Mon Mar 30 14:46:28 2015
Reply to this: 67843
|
|
Category: |
Question |
OS: |
Windows |
ELOG Version: |
ELOG V2.9. |
|
Subject: |
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. |
|
|
|
|