Hi ! Thanks for the answer. But, if it is due to the code, why does it work on another developer computer, with the exact same code ? And why would it work for one tester out of 3 ?
I can't explain that, and as far as I can't explain that, I will not likely consider it is due to the code. Actually, I have absolutely no clue, but I would love to ! On 12 juin, 18:27, mhofmann <rmhofm...@gmail.com> wrote: > Some of my clients have actually seen this, too: > Javascript Error: 'document.body' is null or not an object > > The error line refers to the line "document.body.appendChild( div );" > in jquery.js. > > It has definitely happened for people on IE6, and I believe for people > on IE7 as well... however, it is very sporadic (I've only seen it > happen a handful of times). Maybe it is a race condition, depending > on how/where you include the jquery script, and how you are > initializing the page body? > > On Jun 12, 4:21 am, Lideln <lid...@gmail.com> wrote: > > > Up :) > > > On Jun 10, 6:40 pm, Lideln <lid...@gmail.com> wrote: > > > > Up ! > > > > I really need some help... Am I the only one experiencing such a > > > problem ? > > > I can't use IE6 for now... It's really paralyzing me because I work in > > > a professional environment. > > > > Thank you all for your help ! > > > > On Jun 8, 12:18 pm, Lideln <lid...@gmail.com> wrote: > > > > > Hi, > > > > > Thank you for that long answer ! > > > > > The problem is that on my computer and that of my colleague where it > > > > bugs, we are automatically redirected to the login page. So it'll be > > > > hard to compare the two versions of HTML. > > > > > I also tried to deactivate debugging in IE6 (the two checkboxes in the > > > > options), but nothing new... > > > > > We are two developers, dev_A (me) and dev_B (the one who tests only > > > > with IE7, and where everything works), we have the same SVN up to date > > > > code. > > > > There are 2 colleagues who will test the issue : test_C and test_D. > > > > > If it comes from an IE6 configuration error, why does it work for > > > > test_C when he points to the dev_B machine, and not when it points to > > > > the dev_A (my) machine ? > > > > > If it comes from an apache configuration error, why does it work for > > > > test_D when he points to the dev_A (my) machine ? > > > > > It's really disappointing... I decided ealier (as you advise me now) > > > > to move on, because I can't find a way to correct it, and as it seems > > > > to work for everyone when pointing to the dev_B machine, and because > > > > it only bugs on my machine, only sometimes, and only with IE6. > > > > > On Jun 8, 11:45 am, kranthi <kranthi...@gmail.com> wrote: > > > > > > there is one more thing which i forgot to mention earlier... > > > > > > if i encounter an IE specific error the first thing i do is disable > > > > > all debugging addons in IE, restore all the advanced options to > > > > > default. > > > > > > open the source code in IE of your colleague(on whose computer it is > > > > > working fine). > > > > > open the source code in IE of your computer. > > > > > compare that line by line (use tortoise merge or kdiff) > > > > > > if they dont match... probably u'll be able to find the error. > > > > > if they do match .. that is a configuration prob in your IE(if this is > > > > > the case i recommend you to forget the error and move on) > > > > > > and finally .. > > > > > as far as i know both web developer console and firebug console show > > > > > the same (javascript) errors as that of inbuilt firefox console. they > > > > > only differ when ter is a page refresh. firebug console does not > > > > > "remember" javascript errors of previous pages opened in that browser. > > > > > while web developer console shows "all" javascript errors occoured > > > > > till then.
