Hi, I did some fixes on validations on my local but it dint help much...
I did some more research and learned that, first the main site is loading the jquery.listen.js file and then when I click Glossary, the iframe is also loading the jquery.listen.js file. Could it be that it has to do something with conflicts between those two loads? On Jun 22, 11:49 am, Charlie <charlie...@gmail.com> wrote: > I'm far from an expert but your glossary is using a script to manipulate the > DOM. If DOM isn't valid, scripts manipulating it are likely to have problems. > A lot of behind the scenes repositioning, styling etc occur to tags in > browser when manipulation scripts run so it only makes sense that tag > problems will cause script problems, resulting in page problems > best guess is after you use glossary, browser isn't able to reassemble DOM > exactly, or has memory problems or ......your guess is good as mine > xoail wrote:Yeah now I see the errors... but what I cant understand is why > would it work when I dont click glossary and directly go to search? The issue > only occurs when glossary is used first and then search but if I hit search > before using glossary, it works fine. If it had to do with validations, I > would assume it wont work at all irrespective of whether I use glossary or > not.. but I could be wrong.. my knowledge of javascript and jquery is very > limited so I desperately need some help... I am trying to fix some of those > errors relating to ID values being same... if you can think of anything else > please do let me know. Thanks a lot for helping me with this... On Jun 22, > 9:31 am, Charlie<charlie...@gmail.com>wrote:validator shows recurring ID's > missing script type's, broken tags , invalid style placements, invalid xhtml > tags etc,http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fpjm.comthe > errors part can be seen in web dev toolbar in firefox. Mostly they are > warnings and these seem to be quite common. The interesting part to me was > how often they refresh I profess to not know much about rapidly updating > pages like yours. Validation can cause all sorts of wierd things in DOM > manipulation, likely best place to start xoail wrote:What tool did you use to > see all those errors? I tried firebug and fiddler but they dont show much. > Also, I tried on another PC and I got the same problem with IE7. Thanks! On > Jun 20, 6:04 pm, Charlie<charlie...@gmail.com>wrote:i tried this in IE 7 and > was able to get to search after closing modal without complete lock up page > does however have a significant number of validation errors, multiple use of > ID's, broken tags, invalid xhtml tags ,style tags inside body all over the > place etc and error console keeps throwing about a hundred warnings every > 10-15 seconds some or all of these issues may be causing problems, validation > might help xoail wrote:Anybody? On Jun 19, 3:40 pm, > xoail<mdsoh...@gmail.com>wrote:Hi All, I've been literally pulling my hair > out with this issue I have with our corporate w ebsite. The problem is with > jquery light box (jqmodal) that freezes other controls after use in IE7. > There seem to be no problem with IE6 or FF. If you go to p$j$m.com (remove $ > signs), click Glossary (on top left) close it and then try to use search (top > right), it freezes and then throws an error. Like I said, this issue only > happens in IE7. I have a feeling that something in jqmodal isnt closing and > its conflicting with other controls and IE7 is stupid enough to not identify > and correct it. I would greatly appreciate any help in this regards. Thanks!
