I've written an alternative iOS browser myself, and my guess is this bug is due to the Safari UI misinterpreting the network events that get fired when pages an

I've written an alternative iOS browser myself, and my guess is this bug is due to the Safari UI misinterpreting the network events that get fired when pages and frames are loaded. Wrapping UIWebView makes it really hard to distinguish between page loads and iframe loads to figure out which URL is currently displayed. While Safari uses lower-level interfaces, I'd guess this is happening at a higher-level than webkit, so cross-domain restrictions should still be in place.