Re: 5th manual notes

From: Date: Fri, 17 May 2002 23:19:03 +0000
Subject: Re: 5th manual notes
References: 1  Groups: php.doc.chm 
Request: Send a blank email to php-doc-chm+get-206@lists.php.net to get a copy of this message
You might try to use top.fctname(), and store the function body in a bogus frameset that has only 1 frame ... the html page (if you must have the functions body in every page) I remember having problems with the parent object in JS. Having a fixed, well defined location where you store your code always works smoother. You said the thing about getting way more error reports several times now and I for one think you do not really get the point here (no offense, really). It is clear for me that if there are WAY more error reports, then the code, objects, or something isnt working well. Browsers havent changed, users havent changed ... the only thing that did change was the php chm manual ... kinda speaks for itself. I think you should do some REAL debugging and/or trial error work. Cheers. BoG "Gabor Hojtsy" <gabor@hojtsy.hu> wrote in message news:008101c1fd70$f2a6d9b0$0f00000a@developer2... > > Goba ... why dont you simply rewrite the JS code?? do an > > if statement based on the browser version handling IDs or > > layers or whatever document.unotes is. I don't see it > > being such a big deal. > > a) I use parent.funcname() to call the function on the page, > to show up manual user notes. In some IE versions this also > means, that that function should exaclty be in that file, > and no loaded in from some external JS code. This is why > that function is there in each and every HTML file... > I would not like to make it bigger... > > b) This code was used before since the manual user notes are there, > and the number of reports of such errors were really near zero, > so there may be another problem. > > c) I cannot reproduce the error, so if I rewrite the code, I cannot > test if it works, or not... I need to inject a new sample, and > wait for test results. This is qite a long debug cycle... It > would be way much better to know what exactly is the problem, > and so I can correct it, and can be sure, that it will be OK. > > I hope, I was able to clear up why this is not just some minutes > work. Though I can see that this is a quite significant problem > of many users... > > Goba >

« previous php.doc.chm (#206) next »