• Positioning and alignments of tooltipDialog

    By Fred Husøy 1 decade ago

    We really like the ease to use tooltipDialogs. However the positioning and alignment is not working the same way as the standard dojo versions.

    While the dojo version positions and aligns to always bee within page, the extension library version will position outside the current window if placed close to sides, and always aligns left. The scrollbars will expand, but when trying to reposition view to see the whole dialog, using scrollbars, the dialog disappears.

    Are we doing something wrong or is this default behaviour. We have tried to set dojo.attributes to change alignment, but these seem to have no effect.

    Will this be fixed in future versions?

    • Might be fixed

      By Philippe Riand 1 decade ago

      if we can fix it :-) Can you please investigate and tell us how this is different from the Dojo std behavior you're seeing? Then, we can fix our runtime.

      • Differences in positioning

        By Fred Husøy 1 decade ago

        That would be really great.

        The difference is in positioning and alignment. If we use the ExtLib version the dialog will always position below the anchor and be left-aligned.

        If we use the Dojo version (TooltipDialog) the same way, it will position and align according to the location of the anchor. E.g. if the anchor is on the bottom of the page it will position on the top, and if it is on the right side of the page it will also be right-aligned.

        Please let me know if you need more information or sample code.

        • Yes more info and sample code welcome

          By Philippe Riand 1 decade ago

          It is using the Dojo capability, so what dojo can do we can do :-) Just need to understand what the differences are

          • Sample code

            By Fred Husøy 1 decade ago

            Enclosed you find a document with sample code (code.txt), as well as two images showing differences in positioning between extlib version and dojo version.

            When window is large enough for dialog to display below and to the left, both dialogs displays the same way. When window is smaller, dojo version repositions correct while extlib version requires scrollbar adjustments to view.

            We see same results both in Notes client and web.

            • Thanks,but I think you missed the images

              By Philippe Riand 1 decade ago

              I'd like to see what your issue is as it is not obvious on my machine. FYI, the rendering in 8.5.3, using Dojo 161, looks better positioned than 852 with Dojo 143.

              • tooltipDialog screenshots

                By Nils T Hjelme 1 decade ago
                • tooltipDialog screenshots 2

                  By Nils T Hjelme 1 decade ago
              • Seems to be an issue with Dojo

                By Philippe Riand 1 decade ago

                I can't get a pattern that shows an issue in the extension library. When change the button orders, then I got different problems, whenever this is simple dojo tooltip and updated from the XPage. Are you seeing the same thing?

                • Positioning seems to be solved in 8.5.2.201108212355NTF

                  By Fred Husoy 1 decade ago

                  The positioning seems to be solved in 8.5.2.201108212355NTF, here we see that the extlib control positions correctly on existing pages were it is used, the same way the dojo version does.

                  With this release we however have some problems closing the dialog with a button that worked in earlier releases. First time the dialog opens it does not close with the button, but clicking outside the box closes it. Next time it also closes using button.

                  Regarding the ordering of the buttons in the sample we provided, we find that using only one of the buttons (pre 8.5.2.201108212355NTF) the two dojo buttons positions correctly, while the extlib control always opens dialog bottom and left-aligned as shown in image. All positions correctly in latest build, so this problem seems to be solved.

                  • Nothing changed in the code

                    By Philippe Riand 1 decade ago

                    You might have an issue with the browser cache, as the JS files didn't change in the last build...