similar to: The Autocompleter, with scrollable result-div

Tommy, Every time the Autocomplete results is blur()'d, it adds another onblur event observer (because of "Event.observe(this.update, "blur", this.onBlur.bindAsEventListener(this),true); // make sure blur is still around on") which leads to a performance problem / memory leak. (Commenting it out seems to fix this problem.) I was wondering why it was there? Thanks again,

Hi Ed The reason it adds a new onblur is because when you click the scrollbar the event is gone. I dont know why and how to prevent it, but without adding it back the onblur does not get triggered and the layer does not hide when you click somewhere else on the page. If anyone finds a better solution, please provide a patch. I still have not been able to make the blur work on Safari, so Thomas

you all know the problem with select and textbox in ie6 where you need an iframe under your divs so they will visually be on top. does scriptaculous have api for iframeshim like yahoo yui does? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send

Note that this does not fix gettext for app, that will be done separately in another patch as F10/F11 require different setups for that. In the meantime gettext works if manually changed in environment.rb to gettext_rails instead of gettext/rails Signed-off-by: Jason Guiditta <jason.guiditt at gmail.com> --- src/app/controllers/application.rb | 200 --------

Has anyone extended the Autocompleter to do multiple auto-completes in a single input field? I''m looking to achieve similar functionality to the del.icio.us <http://del.icio.us> post page which allows multiple auto-completes of tag names in the tags input field. cheers, Rob -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi I have a problem with font-face routes on the server,when I open the site in windows, when I do with linux, works . both use chrome latest version. -the fonts are in /assets/fonts/ -in /assets/stylesheets/fonts.css.scss @font-face { font-family: ''OswaldLight''; src: url (''/assets/Oswald-Light-webfont.eot''); src:

Hello all, I noticed that script.aculo.us 1.6.2 supports scrollable divs, and the comments in trac on the http://dev.rubyonrails.org/ticket/4782 patch seem to indicate that this should work in IE. I''ve still running into the problem though -- clicking on the scrollbar in IE is treated as a click outside the autocomplete div. Has anyone had any success with this? jon

Hi, Using the functions in the tcltk library (R1.5.0 Windows, tcltk v1.5.0), does anyone know a simple way to create a list box with a scroll bar? I'm stuck on what to supply to the -xscrollcommand in order to do this but I might be on the wrong track. Best wishes, Jess _____________________________________ Jess Mar Department of Mathematics University of Queensland QLD 4072 AUSTRALIA

Note that one of the 8 patches (#6) will be sent separately in reply to this email, as some of the replaced lines are too long, so git won't let me send the email. However, there is nothing wrong with that patch, and it should be applied in the sequence listed below. Note also that I assume this will be tested on a clean f11 install, rather than an upgrade of an existing ovirt server

Hello everyone: I''ve been using scriptaculous for very long time and it''s really good. However, I just came across another problem about using sortables in a scrollable div. The basic structure is: <div style="overflow:auto; height=400px"> <div id=''Item1''></div> <div id=''Item2''></div> ....

Hi everyone, I have used used scriptalicious for the autocomplete. It works but with one problem. When scrolling down the list, the values not visible are not scrolled into focus. eg I use the keyboard down or up key. Here is my CSS <style type="text/css"> div.auto_complete { height: 100px; width: 350px; background:

I have a fixed height scrollable div inside another div that controls the slideDown and slideUp effects. This causes a really bad flicker in Firefox (1.0.7) for the entire duration of the slide down and up. While on the other hand it works smoothly in IE (except that on a slideUp it causes a last second flash that shows the entire div). Any ideas on how I can fix this? Thanks.

Hi, Are there any plans to "export" the documentation from time to time(e.g. at releases) from the WIKI in an "offline" form to be usable as printed, and/or to be distributed with into scriptaculous-js-1.x.x.zip ? It is very uncomfortable that the ZIP distribution contains practically no documentation :(. Most of the WIKIs have such export function (many of them even export

I''m wondering how i can detect the browser type for the client. I know this is possible, but i cant seem to find how to do this, nor any example code for this. I would appreciate if someone could point me to some info or just give me an explanation. thanks in advance. -------------- next part -------------- An HTML attachment was scrubbed... URL:

After upgrading to prototype 1.5.0 and scriptaculous 1.7.0 my autocompleter.local died... firebug reports that effects.js is to blame calling Element.addMethods(); I can not find out why cause as far as I can see it does exist in prototype.js. Any pointers anyone :( --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups

Hi, If you type a keyword and press Enter in the search field on the wiki, it does a title-search by default which is very limited. I tried looking for information about atheros or madwifi and couldn't find anything. Then I tried ipw2200 (I knew it existed because I created it) and no results still. I had to ask Ralph to see if the index was old, only to find out that there is a

Howdy... How can the text be formated on the downloadable sample (\scriptaculous-js-1.6.1\test\functional\ajax_autocompleter2_test.html)? In your downloadable demo... the format of the drop down (in the txt area) is a ordered list.. where and how is this formatted? and is it possible to use a CSS on it? If so.. how would i do that? I like the formatting you have on your demo

Hello, I am using the AutoCompleter to great effect. However, the site design I have been constrained by has <select> elements/drop down boxes below the AutoCompleter field. This means that in Internet Explorer 6 the drop down elements appear on top of the floating DIV when rendered in the browser. Mozilla floats the DIV on top of the select elements as expected. Has anyone encountered,

Hey there! I''m in the process of looking through the various bug reports and tickets and fixing script.aculo.us as I go along. As I want a 1.6.2 bugfix release to happen this week, please help me out with: - Looking throught the open bugs list on the trac, testing stuff and giving helpful comments (like "+1") - Identifiying what bugs/patches should be included (answer to

Has anyone been able to make scrollable results for an autocompleter? Thanks!