Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...SkinsanitySkinsanity
Previous
 
Next
New Post
7/3/2007 5:21 PM
 

Thanks for the response Timo,

I went in and futzed around with it a bit but then after much good headache I removed every bloody width item from the skin to see what it did without it, then after that I went in and put widths in where needed. Sadly there is still some width issues but for the most part I'm OK with the results I have. Could be better, but heck it is a start.

Thanks again, and thanks to everybody else for helping with my Skinsanity.

 
New Post
3/16/2008 1:32 PM
 

Though it is supposed to be correct in IE8, you need to remember that earlier versions mishandle the box-model.  CSS says that the width you give includes the margin and padding.  However, IE takes the width and uses it for the content on the inside.  Therefore, if you set the width of an object using pixels, the padding and margin are in addition to that.  So a 800px box with 1px margins and 1px padding is actually 804px wide in IE.  This may have something to do with your issues...

 
New Post
3/17/2008 10:38 AM
 

Um, part of the problem is your pagemaster main table is 100% width. I know you setup another table underneath it and set the limit to 800, but if my memory servers me well since your table is essentially in a row fo pagemaster, any cell overflow caused by the subtable IE too wide of rows, / the solpartmenu / Navmenu / modules, can cause the subtable to stretch cause its basically sits in a row that has 100% set for it's width value. Its a weird issue that happens when you nest tables with different width parameters. I remember having this problem a few years ago when building asp sites, use to drive me crazy trying to figure it out. Can't say this will fix your issue but it shouldn't hurt. Its been about 2-3 years since I built any layout with tables, as CSS is much more efficent and easier to control formating with. Not to mention its a requirement for me to make complaint sites, so I can't use tables. Just fyi, inline styling has a different quirk in nearly ever browser, and by default DNN tells all browsers to run in quirks mode. This means IE 7, 6, 5 / mozilla / firefox / opera all render the way they think it should have been done. IE has lots of weird inline style quirks, way to many. lol

Glad to see you are somewhat happy with the layout, but next time set your full exterior table to 800 px, it should force all content regardless that is below it to remain limited to 800px.

 

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...SkinsanitySkinsanity


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out