Shawn, What is the order in which you're importing the js files?
Dan On Dec 3, 7:12 pm, Shawn <[EMAIL PROTECTED]> wrote: > Sorry, maybe this was misleading. I have a form that looks something > like so: > > Employee: ____________________ > > Start Date: ___________________ # > > The employee field would be the autocomplete field, and the start date > would have the date picker. With the dimensions plugin, the calendar > will slide down properly below the date field, but then snap above it. > Not a very large problem - unless the date field is near the top of the > page causing the calendar DIV to have a negative value for it's TOP > position. (making it partly hidden and not accessible). Turning off the > dimensions plugin (removing the script include) makes the date-picker > work properly but now I'm getting the list.scrollTop error when doing > the autocomplete on the employee field. > > I'm digging through my CSS files to make sure I haven't done something > bone-headed, but so far it seems proper... > > Thanks for the input. > > Shawn > > Dan M wrote: > > Shawn, > > > Are you able to "turn off" the auto complete for your date picker > > fields? I couldn't see it being very useful there anyway... > > > Dan > > > On Dec 3, 12:22 am, Shawn <[EMAIL PROTECTED]> wrote: > >> I have a couple of forms that require both an autocomplete field, and a > >> date picker field. I'm using the ui.datepicker and Jorn's autocomplete. > > >> The problem is that Jorn's autocomplete requires the dimensions plugin. > >> When the dimensions plug in is in place, the datepicker is getting > >> given the wrong values for the top position of the calendar. If I take > >> the dimension plugin out, the calendar behaves properly, but the > >> autocomplete throws an error. ( "list.scrollTop is not a function" ). > > >> With dimensions, the calendar slides down as usual, but once sliding is > >> complete the calendar snaps above the text box - with parts of the > >> calendar off the visible area of the page (i.e. hiding behind the > >> toolbars). > > >> Any simple way to resolve this? > > >> Shawn
