ok a bit confused, should I put the register tag in the skin or the container. I am still using the default DNN-Blue / Gray containers, the only thing I created was just the skin. I thought the whole premises of the DNN skinning engine was to completely seperate the skin from the containers / modules. Just trying to figure out why it makes a difference that the content pane uses absolute positioning. The container/module should be the one controlling the menu location based on the containers location within the content pane. I am still new to the skinning aspect of DNN but have been using CSS div tags for website layouts for a long time. Just need to figure out where the connection between skin and container is somehow overlapping. I mean the module is really just a div tag that is nested in the contentpane div tag. Sorry if I am missing something overly obvious and I appreciate all your work around helping me.

I had the same problem ... no solution ... BUT A WORKAROUND:

Place the <dnn:ACTIONS... /> anywhere else in your CSS styled container - try below the title or at the end of your container ... you'll find a place which is not confusing the JavaScript code... - this worked for me (after some research in the code).

Timo: I tried to register a further <dnn:ACTIONBUTTON .../> with the "CommandName" Attribute set to one of the ModuleActionType Consts definied in "DotNetNuke.Entities.Modules.Actions" (e.g. "MoveTop.Action") => I got a compile error. Why is this not working? For "DeleteModule.Action" it works fine an a trash icon is displayed. IMHO this would be easy to implement in ActionButton.vb's Load Event...?