Walter, I had given up on this and switched to jQuery's version of autocompleter, but seeing how I hate jQuery I'm back at it again. I'm working with my SAs to get Firefox/Firebug installed to take a peak behind the scenes.
I just noticed that hitting any non-character button also seems to trigger the correct action. So for instance, I type in "Ja" and my indicator flashes up but no results are displayed. If I hit the shift key once, the correct results for "Ja" are shown. Also, I removed the autocomplete. On Sep 29, 11:29 am, Walter Lee Davis <[EMAIL PROTECTED]> wrote: > I meant that if you were to validate your code, having > autocomplete="false" in the form element would cause it to fail. > > Scripty magically adds the behavior using JavaScript, which is then > valid code. > > Many many things about Prototype (and by extension, Scripty) rely on > your code being squeaky-clean and valid. I am not saying that is the > root of your problem here, just that you should make every attempt to > fix the things that keep a page from validating before calling "bug" > on anything Prototype-based. > > Walter > > On Sep 29, 2008, at 10:07 AM, ericindc wrote: > > > > > > > One other thing, I don't see mention of the invalid attribute in the > > documentation. Can you point me in the right direction... > > > On Sep 26, 12:53 pm, Walter Lee Davis <[EMAIL PROTECTED]> wrote: > >> You don't say if you're having any problems with this, but you can > >> remove the autocomplete (invalid) attribute -- Scripty adds that > >> behavior automagically. Otherwise, this looks okay from the calling > >> side. > > >> If your return includes anything besides a bare list (and these > >> strong tags count, I believe) then you might see failure from there. > >> You're returning a UL, but it's being treated as a data store more > >> than a presentational element. I see what you're trying to accomplish > >> here, but you need to add that style using another means. There is a > >> "hook" event that happens after the autocompleter has refreshed its > >> display. Try patching into that to find and replace the search text > >> within the result list with a 'stronged' version of itself. > > >> Walter > > >> On Sep 26, 2008, at 12:03 PM, ericindc wrote: > > >>> Thanks Walter, that cleared things up. > > >>> Here is a link to the HTML that contains the new Ajax.Autocompleter > >>> code as well as my input field and response div. The PHP script > >>> prints a string of the following format: > > >>> [ul] > >>> [li id="1234"][strong]Perk[/strong]ins, Justin[/li] > >>> [li id="5678"][strong]Perk[/strong]ins, Tim[/li] > >>> [/ul] > > >>>http://pastie.org/279871 > > >>> On Sep 26, 11:18 am, Walter Lee Davis <[EMAIL PROTECTED]> wrote: > >>>> When the Autocompleter says "returns", it means returns in the same > >>>> way that when you request a page from a Web server, the server > >>>> returns that page. It's a HTTP return, not a PHP return. > > >>>> A function (in PHP or any language) may return a string or other > >>>> variable. But that string won't go anywhere outside the application > >>>> server (won't be sent to the browser) unless you print() or echo() > >>>> it. > > >>>> Walter > > >>>> On Sep 25, 2008, at 8:16 PM, ericindc wrote: > > >>>>> The part I was confused on is that my PHP code > >>>>> doesn't actually return the string containing the unordered list, > >>>>> but > >>>>> rather prints it.- Hide quoted text - > > >>>> - Show quoted text -- Hide quoted text - > > >> - Show quoted text -- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~----------~----~----~----~------~----~------~--~---
