please see www.foreverpix.com/webtesting to see this illustrated:
I am using a H1 tag in the title of the module for SEO. I have set the container css for the container title to be the same as the H1 for the font, color, weight etc, so the appearance is the same whether I use the H1 tag or not. But for some reason, using the H1 tag in the module title changes the height of the title area, and moves the actions menu to the line above it.  This has occurred a lot with different containers. I have examined the two in FireBug but cannot see where this is coming from.

Any help appreciated much. thanks.

First, you shouldn't really employ H1 for the module title for all modules on the page. I think for SEO you need just one H1 tag per page. So, if you want the H1 on there, it's more for the page title than module title. You could add the page title to the page enclosed in an H1 tag via the skin. Also, the extra white-space you are getting is from the default padding and/or margins inherent to the H# tags. Try explicitly setting the padding and margins to your tag's css and you'll get that under control.

Secondly, I had the same issue with the module menu jumping to a new line above the title and the visibility button doing the same kind of jumping around. If I recall, it had to do with the title width and the way the div's and css are layed out. I never found a good solution except to go back to using a table for the title/icon/menu/visibility area in a container, that or using fixed width div's that do not "disappear" when they are empty. If someone found a way around that issue with div/css and allows for the "disappearing" item, I'd love to know that solution.

Actually, one solution for the module menu is to add it to a div above the title div. I figured it that menu icon wants to be up, then put it up there. I did that in one container and that div does shrink down when empty. But, I still used a table to place the title, icon, and visibility buttons. Having a fixed width div to the right for the visibility buttons would work in that scenario as long as the project leader is ok with that white-space being there even when the button is not.

---

JOHN GIESY
DotNetNuke Hosting Expert

DotNetNuke 7 Hosting $70 /year
DNN4Less.com Team DotNetNuke  

Thank you very much - removing the & nbsp in the ascx file for the container did it.