|
I had an issue recently using this plug-in in combination with CKEditor where whenever I would select one of it’s built-in drop-down lists, CKEditor would open the down-down list, and then mb_Container would register the mouse click used to open the drop-down (which has is a DIV with absolute positioning) and then mb_Container would execute mb_BringToFront making it impossible to see the drop-down selector as it would then be behind the mb_Container. mb_Container and CKEditor both generate a new z-index, and mb_container would get the higer number each time. The temp solution I have is to comment out the onmousedown call to load mb_BringToFront (on lines 158-160). However, this is a temp solution, as now a container will never come to the front when you click on it if it is behind another container. I was wondering if you had considered this problem of clicking content within the “body” area would be excluded from making a call to mb_BringToFront. I’m not sure of the correct functionality here. I’m using version 2.4 of mb_Container. |
|
Hi Tom, If I exclude the “body” area of the mbContainerPlus from making the call to the mb_bringToFront call than the container will not get the front position once you click on it; I fix this behaviour by adding a new parameter “zIndexContext” to the buildContainers() (default: “auto”) that accept a css selector to specify which DOM elements are affected by the mb_bringToFront() function. This feature is not published yet but you can download the latest release from the gitHub repository: http://github.com/pupunzi/jquery.mb.containerPlus Once you have the latest 2.4.9 release just add: zIndexContext: “.containerPlus” to your buildContainers() function; now mb_bringToFront() will affect only mbContainerPlus elements. |
