Boris Zbarsky wrote: > Michael Vincent van Rantwijk, MultiZilla wrote: >> But this happens on Windows XP and Vista, and Windows 9x is no longer >> supported, right? > > Yes. But the code is not conditioned on OS version. > >> Important new features, like an improved phishing detector for both >> mail and the browser now simply fail because of this bug. > > Feel free to file the bug, yes. > >> Also, the JS component observes "http-on-modify-request" and QI's into >> nsIRequest.name because nsIHttpChannel.referrer can be blocked or >> null, but look at that comment in the IDL; "Often this is the URI of >> the request." so how else do I get to the URI from nsIHttpChannel? > > Uh... you can just get the URI of the nsIChannel. What's the problem > with doing that? And is it me, or is this unrelated to the subject of > this thread?
These were in fact notes to my self (I write notes to my self with things I need to look into) and thus not supposed to be part of my reply. Sorry for that. >> Next problem: How do I get to either the document, docShell, window or >> tab which initiated this request/channel? > > Define "initiated"? You can get the notification callbacks which may or > may not be a docshell. But in general, the question is ill-posed enough > that I don't know how to answer it. And still unrelated to this > thread. ;) > > -Boris Thanks, -- Michael Vincent van Rantwijk - MultiZilla Project Team Lead - XUL Boot Camp Staff member (ActiveState Training Partner) - iPhone Application Developer _______________________________________________ dev-tech-network mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-network
