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 >> >> >> >
