[ http://issues.apache.org/jira/browse/TOBAGO-115?page=comments#action_12434210 ] John Allan commented on TOBAGO-115: -----------------------------------
(Partially Resolved - workaround). The problem was the use of the css/javascript behavior pngBehavior.htc, which modifies img components within the html, so Internet Explorer 6.0 can support PNG transparency. It was actually rewriting the viewId on the fly and assigning graphics and the PngBehavior.htc file itself, to the viewId. When I removed the pngBehavior.htc reference in the code, everything worked fine (even with Ajax). Workaround: I converted all the PNG images to JPG images and removed the behavior. We had used this behavior on our website for years and I've seen references in the myFaces users mailing list to its use with myFaces. I wouldn't have even known what the problem was, until I added a phase listener that displayed viewId after every phase. John > myFaces/Tobago does not work in Internet Explorer on Windows 2000 & 2003 > ------------------------------------------------------------------------ > > Key: TOBAGO-115 > URL: http://issues.apache.org/jira/browse/TOBAGO-115 > Project: MyFaces Tobago > Issue Type: Bug > Affects Versions: 1.0.8 > Environment: Internet Explorer 6 on Windows 2000 Pro, 2000 Server, > 2003 Server > Reporter: John Allan > > The application functions fine within Firefox on Windows XP, Windows 2000 > PRO, Windows 2000 Server, Windows 2003 Server. > The application functions almost correctly exhibits behavior on first click > only within Internet Explorer on Windows XP SP2 > The Application: > Consists of a login screen which verifies against a database and then goes to > a main.jsp page which is composed of 3 tag files. > The main.jsp page has a tabgroup. > Bug: > Login works great, even on problem platforms. > However, once in main.jsp. Clicking on tabs does nothing nor does clicking on > any action buttons. It just refreshes. > I know it sounds like caching behavior, but we have verified cache headers > are outputing correctly and there are no server side caches between the > client and Tomcat running our app. > This has been escalated to Microsoft IE team, as well as their Windows 2000 > team, which has been monitoring the app html communication at length. They > claim the app is simply re-sending the same page and this explains the > behavior. They have verified also that a cache is not involved. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
