Home
Add Issue
List Issues
Complete List
Login#0014 Rendering Problem wth IE6
This following is not a bug in either the HTML or CSS, but a browser incompatiblity which it would be nice to avoid.
IE6 fails to properly render the "Added Issue followup" tbody-div in ShowIssue.zpt. The block gets covered up with the background color of the enclosing trest-div.
An easy fix, although it changes the cosmetics, is to remove the background-color property from the trest selector in screen.css.dtml.
3 years and 4 months and 2 weeks old
Can you help me find a solution which doesn't involve changing the background colour? I'm actually a bit handicapped since I only run Linux on my computers which fortunately doesn't have IE6.
I have the same problem: with Firefox all seems ok, but with IE6 sometimes it goes wrong: Pls look at the attached file, there are 2 screenshots of the same page: I can read the text correctly only if I select it. In the txt file there is the html-source of the page, it could be usefull: the problem is in the div 'tbody'
I will add more information when I will have test your software much more (today is the first day!)
Bye
Alessandro
How about a screenshot image? I don't have a windows computer anymore.
Can you not check out the template with checkoutabletemplates and try to fix it and then let us know?
Sorry the attachment.
I'm tring to check the problem, but I don't know how to use checkoutabletemplates.
The problem is IE; if I pass another window (for example, a wordpad window) on IE the words appear and disappear.. The problem disappear if I remove the class css 'trest' in ShowIssueThreads.zpt, of if I remove or change the class 'threaddate'.
Sometimes only the top-half of the words are written, so I though there was a margin/padding problem, but the problem still persist removing all the line with margin and padding from screen.css.dtml.
Finally this one has been solved. It was my design friend Petter Warnsberg of Swede ltd who solved it. He applied the infamous "Holly hack" for IE6 on Windows.
We managed to reproduce it clearly and after adding a few lines to the bottom of screen.css the problem went away.
These changes are not yet in CVS but will definitely be included in the 0.6.6 release. Thanks all of you.