• Runtime optimized javascript not completely compatible with the extlib?

    By F. Kranenburg 1 decade ago

    I will upload an example database where I use default Extension Library controls. I'm using 8.5.3 with 'use runtime optimized javascript...' option turned on.

    I included a Contentpane that partial refreshes and does a refresh on show. Inside the content pane I have a xp:link and a xe:tooltip. This combination is throwing javascript errors and breaks our application. The error is that the 'dijit.Tooltip' could not be found.

    Now the dijit.Tooltip did not get loaded by the aggregator probably because the content was not initially visible. I know the current workaround to add it to the resources list on the page.

    I wish this could be solved in the Extension Library so it gets more 'fool-proof' ;-).

     

    • and here is the db

      By F. Kranenburg 1 decade ago

      and here is the example database

    • To make a long story short...

      By Philippe Riand 1 decade ago

      I submitted a fix so dojo.require() are execute before dojo actually starts to parse the partial html. This is *not* due to the JS aggregator at all, it fails with it selected or not. This also helped me discover a bug in dojo that I submitted to the dojo team :-)

      Now, you can fix your issue y simply loading extlib.dijit.Tooltip at the page level. Even if the fix above solves the problem, I will still advise you to do it so the module will be part of the aggregated js file. Else, it will be loaded lately using regular dojo loading mechanism.