[Prototype-core] Re: Event.element Problem
Relevant ticket: http://dev.rubyonrails.org/ticket/8397 This has been reported in the issue tracker multiple times, I closed the duplicates. On Dec 12, 2007 8:00 AM, Andrés Robinet [EMAIL PROTECTED] wrote: Hello there, I was experiencing a problem with the Prototype Adapter for ExtJS (http://extjs.com). It happened to me that every time I hit the refresh button in IE 7, I got a JavaScript error popup. Then I tried the fix posted at this link http://extjs.com/forum/showthread.php?p=97978#post97978 by splintor (the last post) as I was using Prototype 1.6. That fixed my problem once and forever. Maybe this is an ExtJS bug which requires patching prototype because it's easier than fixing the adapter... I tried searching the ruby on rails bug tracking system for this bug and didn't find it (Please double check it, I just spent 15 minutes or so trying to find it... maybe it's there, or has another title). Anyway... I just wanted to draw your attention on this, so if this is a Prototype bug you can give it the proper treatment (or you can throw some hints and explanations if this is not a bug, that is also welcome). Thanks in advance, Rob --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype: Core group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~--~~~~--~~--~--~---
[Prototype-core] Re: Event.element Problem
My patch, my patch! Woo hoo! On 12/12/2007, Mislav Marohnić [EMAIL PROTECTED] wrote: Relevant ticket: http://dev.rubyonrails.org/ticket/8397 This has been reported in the issue tracker multiple times, I closed the duplicates. On Dec 12, 2007 8:00 AM, Andrés Robinet [EMAIL PROTECTED] wrote: Hello there, I was experiencing a problem with the Prototype Adapter for ExtJS (http://extjs.com). It happened to me that every time I hit the refresh button in IE 7, I got a JavaScript error popup. Then I tried the fix posted at this link http://extjs.com/forum/showthread.php?p=97978#post97978 by splintor (the last post) as I was using Prototype 1.6. That fixed my problem once and forever. Maybe this is an ExtJS bug which requires patching prototype because it's easier than fixing the adapter... I tried searching the ruby on rails bug tracking system for this bug and didn't find it (Please double check it, I just spent 15 minutes or so trying to find it... maybe it's there, or has another title). Anyway... I just wanted to draw your attention on this, so if this is a Prototype bug you can give it the proper treatment (or you can throw some hints and explanations if this is not a bug, that is also welcome). Thanks in advance, Rob -- - Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498r=213474731 Standing on the shoulders of some very clever giants! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype: Core group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~--~~~~--~~--~--~---
[Prototype-core] Fwd: [prototype-core] Event#unloadCache not available in 1.6.0
(BUMP) Original Message Subject:[prototype-core] Event#unloadCache not available in 1.6.0 Date: Mon, 03 Dec 2007 15:07:03 -0700 From: Ken Snyder [EMAIL PROTECTED] To: prototype-core@googlegroups.com http://groups.google.com/group/rubyonrails-spinoffs/browse_thread/thread/ad88e992ddaceb80 Based on the above discussion on the rails-spinoffs list, I'm wondering if the prototype authors would consider making the destroyCache() functionality available as a public method like Event#unloadCache() was before 1.6.0. Some consider this a compatibility issue and even a bug that should be fixed in 1.6.1. What are your thoughts? Thank you, Ken Snyder --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype: Core group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~--~~~~--~~--~--~---
[Prototype-core] Re: Fwd: [prototype-core] Event#unloadCache not available in 1.6.0
I think our official recommendation is that anyone who needs Event.unloadCache should write it and make its contents the same as that of destroyCache. The code duplication is small enough that it doesn't bother me; anyone who's doing proactive GC probably has written enough JS already that they won't mind an extra five lines. I think we could've handled the 1.6 deprecations a bit better. Sorry if they caught anyone by surprise. Cheers, Andrew On Dec 12, 12:50 pm, Ken Snyder [EMAIL PROTECTED] wrote: (BUMP) Original Message Subject:[prototype-core] Event#unloadCache not available in 1.6.0 Date: Mon, 03 Dec 2007 15:07:03 -0700 From: Ken Snyder [EMAIL PROTECTED] To: prototype-core@googlegroups.com http://groups.google.com/group/rubyonrails-spinoffs/browse_thread/thr... Based on the above discussion on the rails-spinoffs list, I'm wondering if the prototype authors would consider making the destroyCache() functionality available as a public method like Event#unloadCache() was before 1.6.0. Some consider this a compatibility issue and even a bug that should be fixed in 1.6.1. What are your thoughts? Thank you, Ken Snyder --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype: Core group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~--~~~~--~~--~--~---
