Re: 5th manual notes

From: Date: Sun, 19 May 2002 21:08:41 +0000
Subject: Re: 5th manual notes
References: 1 2 3 4 5 6 7  Groups: php.doc.chm 
Request: Send a blank email to php-doc-chm+get-216@lists.php.net to get a copy of this message
I do dev for fun/free also ... No comments on your other statements. Cheers, BoG "Gabor Hojtsy" <gabor@hojtsy.hu> wrote in message news:008501c1ff72$363d34a0$5337a3d5@home... > > Well, that's what usually what users do .. complain. > > You as the developer should bare it and try to solve it (i'm a dev too and > > it wasnt easy at first to bare the complaints). > > Are you paid for that development, or do it in your free time? > > > I think you do ... the "document.unotes" problem ... your id="unotes" > should > > be reffered differently in IE4 and IE5+ (with document.all() and > > document.getelementsbyid() respectively) > > I tried to explain it deeply, but it seems you cannot understand. > > The error is: "document.all.unotes is null or not an object". > On every page there is a <div id="unotes"></div> part, so > on all IE browsers populating that document.all array this > unotes should be registered in that array. > > !! I would like to justify here that I use IE6, yes IE six !! > !! primarily to test the CHM manuals now. !! > > There are quite much evidences, that this IE4 and IE5 switch > is not the right answer to *solve* this problem. > > A) document.all.unotes works quite well, on my IE6, without > *any* errors > > B) noone reported to have this error on **all** pages with user > notes, but document.all.unotes is accessed on all pages, > when there is a corresponding user note HTML file in the > php_manual_notes.chm > > if document.all.unotes would not work on IE5+, then why > it is working on some pages and some machines of users? > > C) the same access method was used in previous chm samples > with user notes included, and there were really few reports > of bugs with it, though many guys reported to use IE5+ (look > at our user survey!!) > > All these factors made me think, that this IS NOT A SOLUTION > for the problem. The code I have copied in one of my last letters > *avoids* this error message by checking first for the > existance of this document element, before accessing it. > > This is not a solution to this problem, as that element should > be there on every page, so checking for it is quite redundant. > > I cannot find why that element is gone on some pages, because > I still cannot reproduce the problem. Those who were able to > reproduce the problem, would not like to provide me any more > information on it. That's it. > > Open Source is about finding pleasure in the work you do, so > you would not like to ask for any money because you love the > thing you do. I cannot find anything I like in this situation > right now.... > > Goba > >

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