The current content filtering implementation suffers from the following problems: - Error pages aren't displayed correctly when a non-HTML document is blocked by the filter. - The filter performs synchronous XPC messaging during loading. - The filter sometimes keeps up to two additional copies of the main resource in memory. - The filter is untestable from a WebKit perspective. This bug tracks improving the content filter by addressing these problems.
<rdar://problem/15097819>