some research info,
type of file, and method of setting appears to be less critical then the headers that the request comes from.
Because .set_html produces an about:blank.html it is headless, which on > Saf5.0.6 appears to restrict local file access. .set_file and .set_url have less issues.
there also appears to have been changes to SU's NSURL settings and recent server-side header changes that affects even v7 with Saf 5.0.3 in some load cases.
but debugging is muddied by the combination of changes. (see attached)some testing
SU's own WebDialogs all appear to be functioning, although the Lion/3D WareHouse login issue may be caused by the same thing.
Knowing what people use Web Dialogs for, I would like the 'SU Team' to give some clear guidance on how all the variables can be made to work together.
an example question I would have, can a client side 'whitelist' (local and external) be set for a WebDialog?
john