Pleeeeease can someone advise on this.. I've been searching Google for a while now but can't find anything concrete which identifies what the issue is.

I'm sure it's a simple one, but I'd appreciate any advice.

When I load any of the pages on the Intranet site I'm building, the jQuery Skin Objects take  a few seconds to load. During that time, the page is automatcially going to the thinest page width I have configured in the skin objects (1024px), but then reverts to the value I've set in the index.ascx page.

Here's my relevant index.ascx code:

<object id="SizeWidget" codetype="dotnetnuke/client" codebase="StyleSheetWidget"
                            declare="declare">
                            <param name="baseUrl" value="<%= SkinPath %>css/variations/" />
                            <param name="template" value="&lt;div title='{TEXT}' {ID} {CLASS}&gt;&lt;/div&gt;" />
                            <param name="default" value="widthfull" />
                            <param name="Width: 1024px" value="width1024" />
                       <!-- <param name="Width: 1280px" value="width1280" />  -->
                            <param name="Browser Width" value="widthfull" />
                        </object>

I'm sure it's not to do with the above as I have the default value set to what I want it to be. Even if I change the default value to 1280, it still goes to 1024px.

FYI - I have the jQuery file local to my server, so it's not downloading it from Google's API Library.

Please can someone tell me what I'm missing here?!

This is one of those situations where I think that the Widgets don't work real well.  The reason is that widgets are not "rendered" until the page has been fully loaded.  Of course, modern browsers begin page rendering as soon as they have any content.  As a result you will have content being displayed long before the page is fully loaded which means it will get displayed using the default styles defined in the head section.  After the page is fully loaded, then the widget takes over and swaps in the new stylesheet.

The solution in this case would be to use a skin object which can read the cookie used by the widget and display the appropriate stylesheet.  This would give you the dynamic switching in the browser without post-back, but would ensure that the default stylesheet rendered from the server is using your cookie to determine the appropriate stylesheet to use.

---

Joe Brinkman
DNN Corp.