I looked at the code and couldn't figure out how to get the behavior
that I thought was correct.
I worked around this by resolving all of my resource references in
the page at the time that I render the page markup. That works, but
it means that I have to walk the DOM and look at every node,
identify all of them that can contain resource references, and
resolve the references the same way I would do if my willSendRequest
delegate were called. It costs me more time to parse and walk the
DOM, and I have this uneasy feeling that I might miss some element
type that contains a resource reference. I'd rather rely on the
browser control to find them for me and call my delegate.
Cheers!
--Chris Ryland / Em Software, Inc. / www.emsoftware.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webkitsdk-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webkitsdk-dev/email@hidden
