Comment 100 for bug 239826

Revision history for this message
In , ashughes (anthony-s-hughes) wrote :

(In reply to comment #76)
> Comment 52 explains the expected behavior.
>
> It can't be guaranteed that view-source isn't exploitable (network calls, HTTP,
> parsing, formatting, linkification, etc etc). As such, view-source on a blocked
> page WILL still show the safebrowsing warning. What this patch does is make the
> buttons on the warning page work, so you can bypass that warning.

That you for taking your time to explain. This is very much appreciated.