Project

General

Profile

Defect #543

Problem with popup menu

Added by Nicola Gervasi over 11 years ago. Updated over 11 years ago.

Status:
New
Priority:
Normal
Assignee:
Patrick Talbot
Start date:
08/14/2012
Due date:
% Done:

0%

Estimated time:
Browser (if web client):
Safari, Chrome (I think all of them)

Description

After plugins.WebClientUtils.addJsReference or plugins.WebClientUtils.addCssReference call popup menus are not working anymore: clicking on the element that should generate the popup simply does nothing (no errors in the log as well), a simple refresh of the browser and they start working ok.

History

#1

Updated by Riccardo Albieri over 11 years ago

  • Assignee set to Patrick Talbot

Same thing on 6.1. Looks like plugins.WebClientUtils.addJsReference('media:///jquery-ui-1.8.17.custom.min.js') causes the popupMenu not to work.

#2

Updated by Patrick Talbot over 11 years ago

Riccardo Albieri wrote:

Same thing on 6.1. Looks like plugins.WebClientUtils.addJsReference('media:///jquery-ui-1.8.17.custom.min.js') causes the popupMenu not to work.

I wonder. Adding a new version of jQuery when jQuery is already injected in the page by Servoy (jQuery 1.5.2) is really not a good idea, so in this case, this could cause all sorts of trouble that the plugin is not going to solve...

#3

Updated by Nicola Gervasi over 11 years ago

It happens when adding jQuery UI, not jQuery. jQuery UI is needed if you want to use stuff like the accordion. Should we create a Servoy case for this issue or do you think it's something related to the plugin itself?

#4

Updated by Patrick Talbot over 11 years ago

OK, sorry, I thought it was jQuery.

Is jQuery-UI 1.8.17 compatible with jQuery 1.5.2?
BTW, they will update jQuery to 1.8.2 in the next Servoy 6.1+ release upon my request.

Also is there no issues with jQuery UI and the build-in Servoy accordion.

I know there is some issues with injecting references but I'm not doing anything different than Servoy does itself to add js references, this is all just regular Wicket code, so I'm wondering what kind of JavaScript conflicts can happen when you inject references in the page after it's initialization.

I need to check first whether something can be done at the plugin level for this or not.

Also available in: Atom PDF