On 20 Jul 2014 09:11, "Erik de Hair" <[email protected]> wrote:
> Hi Dan, > > > The problem looks like [1]. > > Yes, that does look to be the issue. Good bit of archeology! In case you weren't aware, the guy who wrote Select2 - Igor Vaynberg - also wrote the Wicket/Select2 integration that we use, and is one of the most active committers (probably *the* most active) on Apache Wicket itself. With respect to the issue you found, looks like Igor closed the issue waiting for a jsfiddle, which someone subsequently provided. So perhaps you could either ask him to reopen that issue or create a new issue and quote that jsfiddle. Or, looks like there are one or two workarounds mentioned; could always try that also. ~~~ If the worst comes to the worst, then there are other autocomplete widgets that we could integrate with. But I think that Igor is pretty committed (if rather busy), so I think getting him to address this issue is the best option in the short term. Dan > Still have to try your last option. > > Erik > > [1] https://github.com/ivaynberg/select2/issues/1400 > > ________________________________________ > From: Dan Haywood [[email protected]] > Sent: Friday, July 18, 2014 4:37 PM > To: users > Subject: Re: disappearing autocomplete box > > I also wonder if it's anything to do with the size of that action parameter > form? Some sort of scrolling issue? If you shrink (ctrl and -) to 70%, > say, is there a change in behaviour? > > > On 18 July 2014 15:35, Dan Haywood <[email protected]> wrote: > > > Thanks for making the video, very helpful. > > > > Not a known problem, though I do remember coming across some similar > > looking issues with the "select2" component we use, see for example: > > -https://github.com/ivaynberg/select2/issues/550 > > - > > > http://stackoverflow.com/questions/13200987/select2-and-css-transforms-dropdown-menu-is-off-position/13244880#13244880 > > - > > > http://stackoverflow.com/questions/13200987/select2-and-css-transforms-dropdown-menu-is-off-position/13244880#13244880 > > > > Things to try: > > * I see that you've tweaked the CSS. You've probably only made minor > > changes, but just in case there's a conflict, could you revert to the CSS > > in the simple app archetype and double check there problem is still > there? > > * can you use Chrome/Firebug to get more information on the positioning > in > > the case when (a) the drop-down is not positioned correctly, vs (b) when > it > > is. > > * build Isis from source and see if upgrading the widget to use the > > latest-n-greatest version of "select2" sorts out the issue. (Though that > > might introduce other issues, who knows). > > > > Dan > > > > > > > > > > > > On 18 July 2014 15:18, Erik de Hair <[email protected]> wrote: > > > >> Hi, > >> > >> Our application has some forms with an autocomplete box that disappears > >> (Chrome) / moves to the edge of the page (Firefox). See [1] for an > example > >> in Firefox. I've tried this on Windows and Linux. > >> > >> The first time the box opens it moves to the upper left corner and > >> clicking an item doesn't select that item. The second time it all goes > well. > >> > >> Is this a known problem? > >> > >> Thanks, > >> Erik > >> > >> [1] https://www.youtube.com/watch?v=is4qf5oUteo > >> > >> > >> > > >
