2009/9/22 rs21 <ryan.sm...@nrel.gov>: > > Figured it out. I had to go line-by-line through Prototype but there > was a function defined that used the same name as one of the functions > that already existed within the site. Updating the original function > to a new name resolved this bizzare behavior. > > On Sep 18, 2:19 am, "T.J. Crowder" <t...@crowdersoftware.com> wrote: >> Hi, >> >> Your best bet is to try to create a self-contained example >> demonstrating the problem, separate from the site that's behind a >> firewall and code you can't post. More on why this is useful here.[1] >> >> [1]http://proto-scripty.wikidot.com/self-contained-test-page >> >> Good luck, >> -- >> T.J. Crowder >> tj / crowder software / comwww.crowdersoftware.com >> >> On Sep 17, 11:23 pm, rs21 <ryan.sm...@nrel.gov> wrote: >> >> >> >> > I have a site that behaved as designed in both IE and Firefox. I >> > implemented the use of Prototype 1.6.1 for use with flotr for graphing >> > data sets. In IE the functionality of the original site did not >> > degrade after this implementation (in other words everything, >> > including the graphing, functions as expected). However, in Firefox >> > 3.5.2 the graphing works as intended but now portions of the original >> > site are flawed. Specifically elements of forms (such as some, but not >> > all, radio buttons and checkboxes) as well as some elements (images) >> > that use an onClick event. When I click on those elements they just >> > disappear (which is NOT part of the intended functionality) and do not >> > kick off the intended javascript actions. Note that the onClick >> > actions do not call any portion of protoype. These actions existed >> > before prototype's inclusion and they still function in IE 6.0. Also, >> > many of the pages that have disappearing elements do not even use the >> > flotr nor prototype script elements. >> >> > The inclusions within the header that are necessary for flotr are (src >> > path has been truncated for this posting): >> > <!--[if IE]><script type="text/javascript" src="../flotr/ >> > excanvas.js"></script><![endif]--> >> > <script type="text/javascript" src="../flotr/prototype-1.6.1.js"></ >> > script> >> > <script type="text/javascript" src="../flotr/flotr-0.2.0alpha.js"></ >> > script> >> >> > I have narrowed down the problem to the inclusion of the prototype >> > JS. >> >> > Has anyone seen this before? Unfortunately I cannot post a link to the >> > site because it is behind a firewall. I'm also limited in my ability >> > to post the code itself. >> >> > Thanks.- Hide quoted text - >> >> - Show quoted text - > > >
Yet another reason for namespacing Prototype surely? Or should Prototype do a pre-flight check to see if there are any conflicts? We have code dealing with deprecated features. A pre-flight would certainly compliment this. -- ----- Richard Quadling "Standing on the shoulders of some very clever giants!" EE : http://www.experts-exchange.com/M_248814.html Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 ZOPA : http://uk.zopa.com/member/RQuadling --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to prototype-scriptaculous@googlegroups.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~----------~----~----~----~------~----~------~--~---
