Lines Matching refs:interstitial
56 // For malware interstitial pages, we link the problematic URL to Google's
94 // After a malware interstitial where the user opted-in to the report
154 // Only use the V2 page if the interstitial is for a single malware or
155 // phishing resource, the multi-threat interstitial has not been updated to
323 // If the load is blocked, we want to close the interstitial and discard
331 // to a safe page. We will close the interstitial when that page commits.
368 // Note that we cannot just put a link in the interstitial at this point.
369 // It is not OK to navigate in the context of an interstitial page.
434 // received while we were showing the interstitial.
439 // Build an interstitial for all the unsafe resources notifications.
440 // Don't show it now as showing an interstitial while an interstitial is
447 // Now that this interstitial is gone, we can show the new one.
467 // notifications we received while the interstitial was showing.
638 // There are six ways in which the malware interstitial can go
658 // interstitial.
665 // Expanding the "See More" section doesn't finish the interstitial, so
685 // interstitial.
692 // Expanding the "See More" section doesn't finish the interstitial, so
747 InterstitialPage* interstitial =
749 if (interstitial && !unsafe_resource.is_subresource) {
750 // There is already an interstitial showing and we are about to display a
753 interstitial->DontProceed();
754 interstitial = NULL;
757 if (!interstitial) {
758 // There are no interstitial currently showing in that tab, go ahead and
759 // show this interstitial.
772 // This is an interstitial for a page's resource, let's queue it.
957 // TODO(mattm): Implement new multi-threat interstitial and remove
