Hi Joe, I got an answer back from Artisteer support, quoted below. Not unexpected, but still disappointing. I definitely don't think it's right that they are requiring JavaScript functions to run in order to correct layout issues, but that's where we are at this point. I'll email you my support link from Artisteer so you can see the whole exchange.

There are lot of modifications in Artisteer 3 themes.

The issue is reproducible on my side with disabled JS only.
We suggest our customers to not disable scripting to avoid display issues with sidebars, menu separators, etc.

Please note that we do not support mojoPortal and we do not support custom template modifications.

Thanks again,

Jamie

I think it happens with all the atisteer30-* skins included with mojoPortal and all designs exported from Artisteer 3.0. I haven't had a chance yet to look into a workaround solution. I figured Artisteer would not resolve it. In previous versions of Artisteer they supported IE 8 by setting a meta tag to make it work like IE 7, and in the latest version they "support" IE 9 by adding a meta to make it work like IE 8, so they are always behind on IE support in general though that is a separate issue than this IE 7 problem.

I'm sure there must be a way to work around it once I have time to work on it, or maybe Joe D can find a solution.

Best,

Joe

Hi Jamie,

I used Artisteer-30headermenu. Add a width property to the art-content-narrow class. In the skin I tested with, I used 40% because both the side columns were 30% in width (30*2=60, 100-60=40).

Artisteer probably uses javascript to check for the available width and make the column that width. Seems silly to me.

HTH,
Joe D.

Hi Guys,

I was able to fix this and it is now fixed in the source code repository. It turned out to be another difference between Artisteer 3 and previous versions in the CSS classes used in certain scenarios. So the fix actually broke the artisteer24-* skins and this required me to add a configuration property so that we can use different logic in layout.master for Artisteer 3 vs older Artisteer versions.

So basically I added a property on StyleSheetCombiner UseArtisteer3="true" which must be specified in layout.master because the default is false for backward compatibility. The property is not really used inside of StyleSheetCombiner, it is actually used in the code behind for layout.master, but it reads the property value from the StyleSheetCombiner control since that is a convenient place to store style related properties. So after getting the latest code (or after the next release) you would add that in your layout.master and it will fix the layout problem in IE 7.

Best,

Joe

I like Chrome the best myself, it is what I use for day to day work with my own sites. But I use different browsers for different things.

For banking and such I use IE and this about all I use IE for other than testing.

For general surfing and searching and visiting unknown and random web sites or links that people post or send to me I usually use Firefox with the NoScript plugin enabled so that javascript is disabled by default unless I enable it per site that I visit. Since javascript is needed for the vast majority of possible malicious exploits this is a good way to stay safe from malicious sites.

For Facebook, I use Firefox on a separate machine, my old laptop to protect my main machine from risk. I figure the odds of getting infected on Facebook are higher than most other sites because it has so many people the hackers target it all the time.

IE 9 is much better than previous versions, I used it for a few weeks as my main browser to give it a good test, I like it quite a lot, but I still find I like Chrome better.

Best,

Joe