Need a code sample and/or screenshots.

-Jeremy

A side note - using a "sync" call for a URL or XMLHttpRequest will results in failure of the QA process. All network calls must be done via "async" -> had this present inside one of our QA reviews.

Hm, but what about some init loading?
I need load some data BEFORE my widget start. In this case i use "sync" calls now. Is it incorrect?

You will need to find some way around using sync calls. We require data for our widget as well, so we call it during the "onApplicationStartup" event. This gets called before the snippet is even fully loaded, which should give you plenty of time to make the request and receive the response. I have never seen an instance where the data was not received by the time I launch into sidebar mode. If the data is not there, you could put up a wait overlay until it is available, or put up some other indication that data is not currently available.

Sync calls are not good in this environment as they block everything else from executing as Javascript is essentially a single threaded environment. If the sync call never completes, then you have a GUI that is frozen, and the user can't do a thing about it.

Seriously, the "sync" calls should just be removed from the WDK.

That way, one wastes any time trying to implement "sync" calls, only to find out they must rebuild their entire widget structure after an epic FAIL in the QA process. (may or may not be speaking from experience &l )

WidgetRealm, continually flinging mud here on the forums definitely doesn't win you any friends, in fact it does just the opposite. You didn't have to do a major refactor because of "sync" issues alone. If you would like me to air dirty laundry, I'd be happy to share an unbridled opinion of your widgets if that's what you really want, but I personally feel that doesn't do anyone any good. How about instead we work together instead of working against each other?

Friends it is, at least from our end. :m

My point wasn't about positive or negative opinions, but rather that in general one should leave opinions out of the situation when the opinion expressed doesn't add value to the conversation. Talking about "FAIL in QA process" doesn't add any value to a conversation about how a XHR sync issue caused text rendering on screen to be redrawn incorrectly any more than me talking about my opinions of your widget (good or bad).

I guess we needed a new topic...

Only the top three posts involved the Text and the Overlay issue, as we then moved on to assisting with Sync vs Async implementations and the QA repercussions.

Ok, thanks guys. Implemented "async" init loading as Steve said.