similar to: question about auto-updating div with overflow:auto and maintaining position

You should be able to do this by changing the div''s .scrollTop value via javascript (maybe just pick a very large number to ensure bottom is hit, like 10,000). -----Original Message----- From: rails-spinoffs-bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org [mailto:rails-spinoffs-bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org] On Behalf Of Jeremy Kitchen Sent:

No problem! -----Original Message----- From: rails-spinoffs-bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org [mailto:rails-spinoffs-bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org] On Behalf Of Jeremy Kitchen Sent: Wednesday, March 08, 2006 5:39 PM To: rails-spinoffs-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org Subject: Re: [Rails-spinoffs] question about auto-updating

I have this line of code: new Effect.toggle(document.getElementsByClassName(''modarea'', Event.findElement(ev,''li'')), ''blind''); I''ve confirmed that the Effect.toggle is indeed getting the proper element, however, I''m getting this in my javascript console: element.visible is not a function (effects.js: line 153) I

I just ran across this bug when trying to re-create Ben Nolan''s behaviour.js with prototype and was wondering if anyone had fixed it before I went re-inventing the wheel :) Thanks! -Jeremy -- Jeremy Kitchen ++ kitchen-RA8HwDor7flnDGu+y90WmgC/G2K4zDHf@public.gmane.org http://ipaction.org/ -- defend your rights to fair use _______________________________________________

anyone have any information on how to effectively use this? Event.observe() doesn''t return anything, and nothing I''ve tried is actually removing the event listeners from the objects. -Jeremy -- Jeremy Kitchen ++ kitchen-RA8HwDor7flnDGu+y90WmgC/G2K4zDHf@public.gmane.org In the beginning was The Word and The Word was Content-type: text/plain -- The Word of Bob.

Hi folks, I''m pretty new to javascript and prototype, so I just want to get some peer-review on a function I wrote that makes a handy (at least, it seems handy) way to set a group of attributes on an element easily. Object.extend(Element.prototype, { setAttributes: function(attrs) { var el = this; $H(attrs).each( function(attr) { el.setAttribute(attr[0], attr[1]);

Isn''t the difference that the scriptaculous one only gets child nodes from the node you specify, whereas the prototype one gets all in the entire document? Still, it would be nice to just have the one, and let you pass in the document element if you wanted all of them. Just guessing, really. I haven''t looked at the code in question. Greg > -----Original Message----- >

Is there a reason scriptaculous provides what appears to be a redundant function? The reason I''m asking is that it only seems to be used twice throughout all of scriptaculous, and it doesn''t appear to work properly (for some reason it''s returning the actual element, rather than an array with all of the elements) If there is no reason, I''ll modify it to use

No comment on the usefulness of your function, as I''ve yet to try it. But for the "this" scope problem, try this... (removed your var and added the bind(this) after the function declaration. I didn''t test it though so you might want to give it whirl. It might introduce a different scope problem with the "attr" var but I think it should work.

attached is an html file I used to test the bug. the top text box should not allow you to type anything, not tab, not enter, nothing. bottom text box should work fine. requires prototype.js and includes jslog for jslog.info although it only occurs in one place, I just wanted to make sure the event was firing without having to use alerts :) tested browsers/platforms: opera: mac / win / lin:

when using prototype and Class.create(), what''s the preferred method of creating a subclass? say I have a real simple class: var Testing = Class.create(); Object.extend(Testing.prototype, { initialize: function() { ... }, ... }); would I subclass it as so? var SubClass = Class.create(); Object.extend(Object.extend(SubCLass.prototype, Testing.prototype), { ...

Hi folks. I''m working on a project where I need some drag and drop, but I need to implement what happens in a very different way, so I''m creating my own class for it. I don''t want to reinvent the wheel and redo Thomas'' excellent drag/drop functionality, nor do I want to copy/paste his code over into mine. So, I was wondering, has anyone tried to extract

No problem, also check out bindAsEventListener for attaching functions to element events, still maintaining your object as the "this" in the event handler scope at the same time having access to the originating "event" object. In case you haven''t found this resource yet: http://www.sergiopereira.com/articles/prototype.js.html -----Original Message----- From:

Hi, I have a table laid out something like this: <table> <thead> <tr> <th>col 1</th> <th>col 2</th> </tr> </thead> <tbody id="tablebody"> <tr> <td>moo</td> <td>moo</td> </tr> <tr> <td>moo</td> <td>moo</td> </tr>

say I have some code like this: Behaviour.register({ ''#clickme'' : function(el) { Event.observe(el, ''click'', function(event) { alert("clickme was clicked"); }); } }); Behaviour.apply(); Behaviour.apply(); the element with the id of ''clickme'' will now have 3 onclick event observers. Is there a way to work around this? I

I noticed that prototype.js defines a shift() method for the Array prototype. The base prototype already defines this method, is there a reason it is being redefined in prototype? Maybe certain browsers aren''t implementing the shift() method? If that''s the case, shouldn''t there also be an unshift()? :) Thanks! -Jeremy -- Jeremy Kitchen ++

I thought the duration parameter was only used with Effect functions, but I could be wrong. Greg > -----Original Message----- > From: rails-spinoffs-bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org [mailto:rails-spinoffs- > bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org] On Behalf Of Joe Hudson > Sent: Tuesday, April 25, 2006 8:37 AM > To:

I''m using prototype 1.4.0 in a big web application I''ve been working on for months and today a bug was raised by one of our testers. After investigation it turns out that something done 0 times will actually fire once. So, for example, if I had (0).times( function(i) { alert(i); } ); it''d fire once rather than not at all. Is this a bug in prototype or the

Hi All, I am working on a page that has 4 configuration sections at the bottom of the page with 4 links to them higher up on the page. We are using the Effects.BlindDown to show the lower section when the corresponding link is clicked. We also use the "new Effects.ScrollTo(''DIVTag'')" to have the page scroll to the newly opened section. Now this works fine in

Is there a way to throttle the firing of updater requests easily with Prototype? Thanks, mark