You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(75) |
Nov
(252) |
Dec
(418) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(659) |
Feb
(1039) |
Mar
(870) |
Apr
(235) |
May
(329) |
Jun
(251) |
Jul
(123) |
Aug
(119) |
Sep
(67) |
Oct
(194) |
Nov
(535) |
Dec
(133) |
2002 |
Jan
(122) |
Feb
(24) |
Mar
(29) |
Apr
(28) |
May
(16) |
Jun
(20) |
Jul
(11) |
Aug
(12) |
Sep
(13) |
Oct
(14) |
Nov
(23) |
Dec
(19) |
2003 |
Jan
(28) |
Feb
(170) |
Mar
(288) |
Apr
(211) |
May
(126) |
Jun
(166) |
Jul
(131) |
Aug
(102) |
Sep
(211) |
Oct
(301) |
Nov
(22) |
Dec
(6) |
2004 |
Jan
(14) |
Feb
(16) |
Mar
(7) |
Apr
|
May
(8) |
Jun
(25) |
Jul
(21) |
Aug
(2) |
Sep
(7) |
Oct
|
Nov
(2) |
Dec
(1) |
2005 |
Jan
(4) |
Feb
(2) |
Mar
(14) |
Apr
(24) |
May
(3) |
Jun
(7) |
Jul
(30) |
Aug
(5) |
Sep
(1) |
Oct
(3) |
Nov
|
Dec
(1) |
2006 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
From: Patricia F. <tec...@ca...> - 2001-01-17 16:52:21
|
I've been looking through the mailing lists and wasn't able to find an answer to my problem, so after trying around for three intensive days I'm posting it along with the example files in a Zip file (Pruebas.zip): I'm working with the new DynApi. I've a frames construction as follows: frame "margen" contains a page called margenJS.htm which contains all of the api libs and the DynApi.onload function. I've added a folder called "aries" into the dynacore folder, which contains all of my code, so I can use the include() method for those files also. Into that folder there are two files beeing used: menuAries.js: contains the DynDocument construction for the frames, and the corePopUp construction. frame "datos1"contains a page called margen_datos1.htm, which contanis an array of elements, which are the items that have to be added to the corePopUp. frame "estado" is the frame where the corePopUp is added. THE PROBLEM Everything works good as long as I don't load a different page into the frame "estado". When this is done, it won't send an error, but the CorePuoUp won't pop. So I tried to execute the addChild(myPopUp1) method again when a new page is loaded, and i got the message: "Attempt to add "'+child.id+'" to the document "'+this.dyndoc.id+'" failed.\n\nThe DynLayer already exists in that DynDocument.\n\nYou must remove the dynlayer from its parent first." So, I wonder why if everything exists, it doesn't show. Also I was writing alerts everywhere, and it will execute, the CorePopUp is set to visible, the z-index, etc. but it doesn't show....where the ! is it poping up?!!!!!!!!!!!!!!!!!! ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- --------- another problem I had (by the way!) When I started using this Construction in the beginnning, everything was the same it is now, but the corePopUp coonstruction. Now I'm puting all the "myPopUp1.add()" sentences into a function called cargaMenu(). I'm calling that function from the DynApi.onload= function(){}. I made it this way, because otherwise, the myPopUp1.add() method was working only the first time I executed it after the computer was started, and never again! ONLY after the computer was restarted, if i restarted only the user session it wouldn't work neither. The corePopUp was working, but it wasn't adding the items. P.D.: I'm a designer who is working with JavaScript since a couple of months, so I'm not that skilled yet. Thanks a lot. Pat |
From: Patricia F. <tec...@ca...> - 2001-01-17 16:48:51
|
I've been looking through the mailing lists and wasn't able to find an answer to my problem, so after trying around for three intensive days I'm posting it along with the example files in a Zip file (Pruebas.zip): I'm working with the new DynApi. I've a frames construction as follows: frame "margen" contains a page called margenJS.htm which contains all of the api libs and the DynApi.onload function. I've added a folder called "aries" into the dynacore folder, which contains all of my code, so I can use the include() method for those files also. Into that folder there are two files beeing used: menuAries.js: contains the DynDocument construction for the frames, and the corePopUp construction. frame "datos1"contains a page called margen_datos1.htm, which contanis an array of elements, which are the items that have to be added to the corePopUp. frame "estado" is the frame where the corePopUp is added. THE PROBLEM Everything works good as long as I don't load a different page into the frame "estado". When this is done, it won't send an error, but the CorePuoUp won't pop. So I tried to execute the addChild(myPopUp1) method again when a new page is loaded, and i got the message: "Attempt to add "'+child.id+'" to the document "'+this.dyndoc.id+'" failed.\n\nThe DynLayer already exists in that DynDocument.\n\nYou must remove the dynlayer from its parent first." So, I wonder why if everything exists, it doesn't show. Also I was writing alerts everywhere, and it will execute, the CorePopUp is set to visible, the z-index, etc. but it doesn't show....where the ! is it poping up?!!!!!!!!!!!!!!!!!! ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- --------- another problem I had (by the way!) When I started using this Construction in the beginnning, everything was the same it is now, but the corePopUp coonstruction. Now I'm puting all the "myPopUp1.add()" sentences into a function called cargaMenu(). I'm calling that function from the DynApi.onload= function(){}. I made it this way, because otherwise, the myPopUp1.add() method was working only the first time I executed it after the computer was started, and never again! ONLY after the computer was restarted, if i restarted only the user session it wouldn't work neither. The corePopUp was working, but it wasn't adding the items. P.D.: I'm a designer who is working with JavaScript since a couple of months, so I'm not that skilled yet. Thanks a lot. Pat |
From: <cam...@ya...> - 2001-01-17 16:31:15
|
Hmm, I don't have a straight forward example (the DynImage's I'm using are buried in everything else I'm working on at the moment). I'll try and come up with an example. --- Robert Rainwater <rra...@ya...> wrote: > > I'm using IE 5.5 sp1 and the image size returned > from DynImage is > always correct when I do not pass an image size. Do > you have an > example where this is not working? > > -- > // Robert Rainwater > > On 1/17/2001, 6:23:12 AM EST, noreply wrote about > "[Dynapi-Dev] [Bug #129040] DynImage default image > size incorrect in IE5.5": > > > Bug #129040, was updated on 2001-Jan-16 11:08 > > Here is a current snapshot of the bug. > > > Project: DynAPI 2 > > Category: None > > Status: Open > > Resolution: None > > Bug Group: None > > Priority: 5 > > Submitted by: camhart > > Assigned to : nobody > > Summary: DynImage default image size incorrect in > IE5.5 > > > Details: When creating a DynImage without setting > a size, IE5.5 always > > defaults to the same (incorrect) size. > > > I'm not sure where IE5.5 is getting this size > from. This bug may apply to > > IE5 also. > > > Follow-Ups: > > > Date: 2001-Jan-17 03:23 > > By: nobody > > > Comment: > > It appears that the incorrect height and width is > being returned by > > getContentHeight and getContentWidth in > dynlayer.js. It to be returning a > > default of w=28 and h=30. > > > ------------------------------------------------------- > > > For detailed info, follow this link: > > > http://sourceforge.net/bugs/?func=detailbug&bug_id=129040&group_id=5757 > > > _______________________________________________ > > Dynapi-Dev mailing list > > Dyn...@li... > > > http://lists.sourceforge.net/lists/listinfo/dynapi-dev > > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev > > __________________________________________________ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/ |
From: Robert R. <rra...@ya...> - 2001-01-17 16:06:29
|
I found a few ways to make the List widget improve speed wise. However, the widget is still terribly slow to rewrite the layers. Any suggestions to improve the number of layer rewriting that goes on (make it less I mean). I suspect the layer rewriting (setHTML) is what is causing the list widget to muck up. -- // Robert Rainwater |
From: Robert R. <rra...@ya...> - 2001-01-17 15:33:13
|
I'm using IE 5.5 sp1 and the image size returned from DynImage is always correct when I do not pass an image size. Do you have an example where this is not working? -- // Robert Rainwater On 1/17/2001, 6:23:12 AM EST, noreply wrote about "[Dynapi-Dev] [Bug #129040] DynImage default image size incorrect in IE5.5": > Bug #129040, was updated on 2001-Jan-16 11:08 > Here is a current snapshot of the bug. > Project: DynAPI 2 > Category: None > Status: Open > Resolution: None > Bug Group: None > Priority: 5 > Submitted by: camhart > Assigned to : nobody > Summary: DynImage default image size incorrect in IE5.5 > Details: When creating a DynImage without setting a size, IE5.5 always > defaults to the same (incorrect) size. > I'm not sure where IE5.5 is getting this size from. This bug may apply to > IE5 also. > Follow-Ups: > Date: 2001-Jan-17 03:23 > By: nobody > Comment: > It appears that the incorrect height and width is being returned by > getContentHeight and getContentWidth in dynlayer.js. It to be returning a > default of w=28 and h=30. > ------------------------------------------------------- > For detailed info, follow this link: > http://sourceforge.net/bugs/?func=detailbug&bug_id=129040&group_id=5757 > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev |
From: <cam...@ya...> - 2001-01-17 14:40:10
|
Hi, I've attached my modified LoadPanel that I've got working with Mozilla (0.7) on PC. I don't see any reason why it won't work in Netscape 6, and Mozilla on other platforms, but I don't have access to NS6 or a Mac/Linux box to test. Presumably as this code is based on DOM1, it might also work in Mac IE5 with some tweaking. It works with the loadpanel test in CVS. One thing that doesn't work is autoresize. This is not LoadPanel's fault, it's because getContentWidth and getContentHeight don't work in Netscape 6. It would be great if this could make it's way into CVS (if it works for everyone else!). I could submit a patch if it would help. Cheers, Cameron. __________________________________________________ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/ |
From: <no...@so...> - 2001-01-17 11:23:15
|
Bug #129040, was updated on 2001-Jan-16 11:08 Here is a current snapshot of the bug. Project: DynAPI 2 Category: None Status: Open Resolution: None Bug Group: None Priority: 5 Submitted by: camhart Assigned to : nobody Summary: DynImage default image size incorrect in IE5.5 Details: When creating a DynImage without setting a size, IE5.5 always defaults to the same (incorrect) size. I'm not sure where IE5.5 is getting this size from. This bug may apply to IE5 also. Follow-Ups: Date: 2001-Jan-17 03:23 By: nobody Comment: It appears that the incorrect height and width is being returned by getContentHeight and getContentWidth in dynlayer.js. It to be returning a default of w=28 and h=30. ------------------------------------------------------- For detailed info, follow this link: http://sourceforge.net/bugs/?func=detailbug&bug_id=129040&group_id=5757 |
From: Michael P. <mp...@ph...> - 2001-01-17 05:25:05
|
There are a few points in the events.js that have an if statement for IE and then an if statement for NS4. I know that this is only a small matter and doesn't solve (or cause) any bugs, but i suggest that they be replace with IF.. ELSE IF statements. This way, IE doesn't need to check for NS after it has executed it's own code. -- Michael Pemberton mp...@ph... ICQ: 12107010 |
From: <no...@so...> - 2001-01-16 19:08:15
|
Bug #129040, was updated on 2001-Jan-16 11:08 Here is a current snapshot of the bug. Project: DynAPI 2 Category: None Status: Open Resolution: None Bug Group: None Priority: 5 Submitted by: camhart Assigned to : nobody Summary: DynImage default image size incorrect in IE5.5 Details: When creating a DynImage without setting a size, IE5.5 always defaults to the same (incorrect) size. I'm not sure where IE5.5 is getting this size from. This bug may apply to IE5 also. For detailed info, follow this link: http://sourceforge.net/bugs/?func=detailbug&bug_id=129040&group_id=5757 |
From: <no...@so...> - 2001-01-16 19:04:05
|
Bug #128748, was updated on 2001-Jan-14 11:07 Here is a current snapshot of the bug. Project: DynAPI 2 Category: Core API Status: Open Resolution: None Bug Group: None Priority: 5 Submitted by: eytanh Assigned to : nobody Summary: Mouse Events Details: I have found this in IE 5 and NS 4. If you try to use an event handler and you try to call e.x or e.getX or e.getPageX. (or instead of x y) you get a madeup result. (-1 all the time). I think the problem is with these lines: this.pageX=is.ie?e.x+document.body.scrollLeft:e.pageX-window.pageXOffset; this.pageY=is.ie?e.y+document.body.scrollTop:e.pageY-window.pageYOffset; this.x=is.ie?e.offsetX:e.layerX; this.y=is.ie?e.offsetY:e.layerY; I have a feeling that some of these variables are undefined and thus resulting in inaccurate results. On the other hand if instead of trying to call e.getX(); you call e.orig.x it works. Follow-Ups: Date: 2001-Jan-16 11:04 By: dcpascal Comment: Which mouseevent are you trying it on? I've just tested in IE5 (win32) with latest CVS code, and it works correctly.. could you show some example code ------------------------------------------------------- For detailed info, follow this link: http://sourceforge.net/bugs/?func=detailbug&bug_id=128748&group_id=5757 |
From: <no...@so...> - 2001-01-16 18:42:59
|
Patch #103153 has been updated. Project: dynapi Category: DynAPI-Widget Status: Closed Submitted by: digitalstrider Assigned to : nobody Summary: ButtonImage.js Follow-Ups: Date: 2001-Jan-16 10:42 By: rainwater Comment: This patch has been implemented in the current CVS source. ------------------------------------------------------- ------------------------------------------------------- For more info, visit: http://sourceforge.net/patch/?func=detailpatch&patch_id=103153&group_id=5757 |
From: <no...@so...> - 2001-01-16 18:41:01
|
Bug #129033, was updated on 2001-Jan-16 10:40 Here is a current snapshot of the bug. Project: DynAPI 2 Category: API Extentions Status: Open Resolution: None Bug Group: None Priority: 5 Submitted by: camhart Assigned to : nobody Summary: new DynImage('src') does not always find src in loadimages Details: When you create a new DynImage from a path, it checks the loadimages array for an image with the that path that exists already. i've been creating dynimages by passing an absolute path to the image without the host part. because the browser adds the host to src in the image object, when i create a new dynimage from the same path my image is not found in loadimages array. here's an example: myImage1 = new DynImage('/images/button.gif'); Now DynImage.loadimages has one image in it. myImage2 = new DynImage('/images/button.gif'); DynImage.loadimages now has 2 images in it, because when it was looking for '/images/button.gif' it only found 'http://hostname/images/button.gif' I modifed DynImage.getImage to fix the problem. It seems to work, here's my new function: DynImage.getImage=function(src,w,h) { for (var i=0;i<DynImage.loadimages.length;i++) { if (DynImage.loadimages[i].img.src_orig==src) { return DynImage.loadimages[i].img; } } DynImage.loadimages[i] = {}; if (w&&h) DynImage.loadimages[i].img = new Image(w,h); else DynImage.loadimages[i].img = new Image(); DynImage.loadimages[i].complete = false; DynImage.loadimages[i].img.src=DynImage.loadimages[i].img.src_orig=src; return DynImage.loadimages[i].img; }; For detailed info, follow this link: http://sourceforge.net/bugs/?func=detailbug&bug_id=129033&group_id=5757 |
From: <cam...@ya...> - 2001-01-16 18:09:12
|
I've just been having a quick play around with dynimage, and noticed that in ie5.5 the image size is being set incorrectly. all the images seem to be getting set to the same size no matter what their true size is. netscape seems to work fine. There is another problem with DynImage that I noticed. When you create a new DynImage, it checks the loadimages array for an image object that exists already. i've been creating dynimages by passing an absolute path to the image without the host part. the browser adds the host to the src in the image object. so when i create a new dynimage from the same src, my image is not found in loadimages array. here's an example: myImage1 = new DynImage('/images/button.gif'); Now DynImage.loadimages has one image in it. myImage2 = new DynImage('/images/button.gif'); DynImage.loadimages now has 2 images in it, because when it was looking for '/images/button.gif' it only found 'http://hostname/images/button.gif' One way of fixing this would be to store the src_orig as well as the src. src_orig wouldn't get changed by the browser. hope all this is of use to someone out there ;-) cam. __________________________________________________ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/ |
From: Robert R. <rra...@ya...> - 2001-01-16 17:08:46
|
The snapshot should now re-include the jspacked files as of the latest update. Because of the Sourceforge server having problems, I had previously removed the jpack build. Please check the jspacked files for semicolon errors so we can include the compressed files in the next release. -- // Robert Rainwater |
From: <no...@so...> - 2001-01-15 18:11:21
|
Bug #128575, was updated on 2001-Jan-12 10:20 Here is a current snapshot of the bug. Project: DynAPI 2 Category: Browser-Specific Issue Status: Closed Resolution: Wont Fix Bug Group: None Priority: 5 Submitted by: mortendk Assigned to : nobody Summary: Mac a Doctype Bug Details: kinda strange bug this one IE5(mac): if you set the Doc type tag as it schould be written: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd"> the browser dont display any of the layers (or divs - whatever you know what i mean ;-]) i tested it on a IE4.5 and there the layers are displayed correct. What courses the problem in IE5 are the "http://" in the second line. A work around this problem is to remove the http:// from the doctype when you page is viewed in a ie5 on the mac: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "www.w3.org/TR/1999/REC-html401-19991224/loose.dtd"> Follow-Ups: Date: 2001-Jan-15 10:11 By: mortendk Comment: it works fine when you leave the doctype part out - maybe its the same as Bug #126673 (but the unknown person who submited it didnt leave much info so im not sure) Just leave the doctype out when it is wied on a mac/IE 5 -then its working fine. ------------------------------------------------------- Date: 2001-Jan-15 09:48 By: dcpascal Comment: The DynAPI does no checking for meta tags or anything, the browser is the only thing checking for it. Both cases are IE browsers. If you leave the !DOCTYPE part out, does it work then? ------------------------------------------------------- Date: 2001-Jan-15 09:28 By: ckepper Comment: I checked this out on a Mac with IE 5.0 (2022) and it didn't work. Maybe it's more than just a browser bug? Mmmh. I think that this might be the same problem as Bug #126673. ------------------------------------------------------- Date: 2001-Jan-12 11:12 By: dcpascal Comment: Not a DynAPI bug, but a browser bug ------------------------------------------------------- For detailed info, follow this link: http://sourceforge.net/bugs/?func=detailbug&bug_id=128575&group_id=5757 |
From: <no...@so...> - 2001-01-15 17:48:13
|
Bug #128575, was updated on 2001-Jan-12 10:20 Here is a current snapshot of the bug. Project: DynAPI 2 Category: Browser-Specific Issue Status: Closed Resolution: Wont Fix Bug Group: None Priority: 5 Submitted by: mortendk Assigned to : nobody Summary: Mac a Doctype Bug Details: kinda strange bug this one IE5(mac): if you set the Doc type tag as it schould be written: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd"> the browser dont display any of the layers (or divs - whatever you know what i mean ;-]) i tested it on a IE4.5 and there the layers are displayed correct. What courses the problem in IE5 are the "http://" in the second line. A work around this problem is to remove the http:// from the doctype when you page is viewed in a ie5 on the mac: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "www.w3.org/TR/1999/REC-html401-19991224/loose.dtd"> Follow-Ups: Date: 2001-Jan-15 09:48 By: dcpascal Comment: The DynAPI does no checking for meta tags or anything, the browser is the only thing checking for it. Both cases are IE browsers. If you leave the !DOCTYPE part out, does it work then? ------------------------------------------------------- Date: 2001-Jan-15 09:28 By: ckepper Comment: I checked this out on a Mac with IE 5.0 (2022) and it didn't work. Maybe it's more than just a browser bug? Mmmh. I think that this might be the same problem as Bug #126673. ------------------------------------------------------- Date: 2001-Jan-12 11:12 By: dcpascal Comment: Not a DynAPI bug, but a browser bug ------------------------------------------------------- For detailed info, follow this link: http://sourceforge.net/bugs/?func=detailbug&bug_id=128575&group_id=5757 |
From: <no...@so...> - 2001-01-15 17:44:54
|
Bug #126673, was updated on 2000-Dec-22 03:23 Here is a current snapshot of the bug. Project: DynAPI 2 Category: Browser-Specific Issue Status: Open Resolution: None Bug Group: None Priority: 5 Submitted by: nobody Assigned to : nobody Summary: IE 4 & 5 Macintosh Details: DynLayer doesn't work properly Follow-Ups: Date: 2001-Jan-15 09:44 By: dcpascal Comment: Someone with Mac IE access that can fix this? or: Any other Mac IE users who have the same problems (or no problems at all) ------------------------------------------------------- Date: 2001-Jan-15 09:12 By: ckepper Comment: As far as I can see there must be something wrong with the initialization routine of the Dynlayer. I don't get any Javascript Error Messages and the Dynlayers don't show up anywhere. However, everything worked fine in all other browsers. ------------------------------------------------------- Date: 2001-Jan-12 11:18 By: dcpascal Comment: Give more info, cause this is not helpfull. ------------------------------------------------------- For detailed info, follow this link: http://sourceforge.net/bugs/?func=detailbug&bug_id=126673&group_id=5757 |
From: <no...@so...> - 2001-01-15 17:28:44
|
Bug #128575, was updated on 2001-Jan-12 10:20 Here is a current snapshot of the bug. Project: DynAPI 2 Category: Browser-Specific Issue Status: Closed Resolution: Wont Fix Bug Group: None Priority: 5 Submitted by: mortendk Assigned to : nobody Summary: Mac a Doctype Bug Details: kinda strange bug this one IE5(mac): if you set the Doc type tag as it schould be written: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd"> the browser dont display any of the layers (or divs - whatever you know what i mean ;-]) i tested it on a IE4.5 and there the layers are displayed correct. What courses the problem in IE5 are the "http://" in the second line. A work around this problem is to remove the http:// from the doctype when you page is viewed in a ie5 on the mac: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "www.w3.org/TR/1999/REC-html401-19991224/loose.dtd"> Follow-Ups: Date: 2001-Jan-15 09:28 By: ckepper Comment: I checked this out on a Mac with IE 5.0 (2022) and it didn't work. Maybe it's more than just a browser bug? Mmmh. I think that this might be the same problem as Bug #126673. ------------------------------------------------------- Date: 2001-Jan-12 11:12 By: dcpascal Comment: Not a DynAPI bug, but a browser bug ------------------------------------------------------- For detailed info, follow this link: http://sourceforge.net/bugs/?func=detailbug&bug_id=128575&group_id=5757 |
From: Dann <da...@to...> - 2001-01-15 17:16:03
|
Hi, Perhaps this is something that should find its way in the FAQ sheet, but I have found this behaviour to occur when you use the DOCTYPE declaration on certain platforms. I have read on this list that IE on Mac is vulnerable to problem this too... I'm not sure this will help you in your particular case, but at least it's a checkmark you can put on the list of possible problems. CU, Dann Christoph Kepper wrote: > As far as I can see there must be something wrong with the initialization > routine of the Dynlayer. I don't get any Javascript Error Messages and the > Dynlayers don't show up anywhere. However, everything worked fine in all > other browsers. > > I used a standard(simple) dynlayer and several customized versions of the > PopUp-Widget and always had the same problem: everything is working fine in > all browsers EXCEPT in IE for Mac. > > So far I didn't dig to into the initialization routines, but I could do some > testing on the Mac IE. > > Christoph > > ===================================================== > Die Firma - Ges. fuer innovative Kommunikation mbH > Schwalbacher Str. 74 . 65183 Wiesbaden . Germany > Vox +49 (611) 238 50 10 . Fax +49 (611) 238 50 10 > http://www.diefirma.de . mailto:c.k...@di... > > NEW! Startup-Initiative: http://www.starthilfe.net > ===================================================== > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev |
From: <no...@so...> - 2001-01-15 17:12:37
|
Bug #126673, was updated on 2000-Dec-22 03:23 Here is a current snapshot of the bug. Project: DynAPI 2 Category: Browser-Specific Issue Status: Closed Resolution: Invalid Bug Group: None Priority: 5 Submitted by: nobody Assigned to : nobody Summary: IE 4 & 5 Macintosh Details: DynLayer doesn't work properly Follow-Ups: Date: 2001-Jan-15 09:12 By: ckepper Comment: As far as I can see there must be something wrong with the initialization routine of the Dynlayer. I don't get any Javascript Error Messages and the Dynlayers don't show up anywhere. However, everything worked fine in all other browsers. ------------------------------------------------------- Date: 2001-Jan-12 11:18 By: dcpascal Comment: Give more info, cause this is not helpfull. ------------------------------------------------------- For detailed info, follow this link: http://sourceforge.net/bugs/?func=detailbug&bug_id=126673&group_id=5757 |
From: Christoph K. <c.k...@di...> - 2001-01-15 17:09:52
|
As far as I can see there must be something wrong with the initialization routine of the Dynlayer. I don't get any Javascript Error Messages and the Dynlayers don't show up anywhere. However, everything worked fine in all other browsers. I used a standard(simple) dynlayer and several customized versions of the PopUp-Widget and always had the same problem: everything is working fine in all browsers EXCEPT in IE for Mac. So far I didn't dig to into the initialization routines, but I could do some testing on the Mac IE. Christoph ===================================================== Die Firma - Ges. fuer innovative Kommunikation mbH Schwalbacher Str. 74 . 65183 Wiesbaden . Germany Vox +49 (611) 238 50 10 . Fax +49 (611) 238 50 10 http://www.diefirma.de . mailto:c.k...@di... NEW! Startup-Initiative: http://www.starthilfe.net ===================================================== |
From: Dann <da...@to...> - 2001-01-15 16:11:00
|
Hi, ... it works fine now - no more flicker, ever since dat skinwindow appeared on the page... CU, Dann |
From: Doug M. <do...@cr...> - 2001-01-15 15:59:22
|
> Hi, > > True... I'm running legacy here... hold on, have to throw more coal in the > oven... :) Still... is the display actually being altered at each instance by > the API, or is it just a bad case of browseritis... ? Do you mean the menus? If so, it's 'cause the mouseover for the menu buttons call HidePop as well as ShopPop.. I had to add code to ensure that if we are over pop1 and are already showing pop1 then do nothing. It should work a little better. > > Don't despair, my stuff also *nearly* works :) LOL ! > > CU, > Dann > |
From: Dann <da...@to...> - 2001-01-15 15:57:38
|
Hi, ... It works great in IE5.0 - it's a strain on the eyes in NS4.73... (after your alteration). CU, Dann |
From: Dann <da...@to...> - 2001-01-15 15:54:06
|
Hi, True... I'm running legacy here... hold on, have to throw more coal in the oven... :) Still... is the display actually being altered at each instance by the API, or is it just a bad case of browseritis... ? Don't despair, my stuff also *nearly* works :) LOL ! CU, Dann |